Operational Defect Database

BugZero found this defect 2501 days ago.

MongoDB | 375593

[SERVER-28868] Set noCursorTimeout option on oplog cursor in ReplSetTest.prototype.checkOplogs()

Last update date:

10/30/2023

Affected products:

MongoDB Server

Affected releases:

3.4.0-rc0

Fixed releases:

3.4.5

3.5.7

Description:

Info

It is possible that a test sets the "cursorTimeoutMillis" server parameter to a small value and never resets it to the default value of 10 minutes. Running the run_check_repl_oplog.js check after one of these tests can cause the cursor on the oplog to time out. We should set the noCursorTimeout option on the oplog cursor to prevent it from timing out.

Top User Comments

xgen-internal-githook commented on Thu, 20 Apr 2017 23:03:59 +0000: Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'} Message: SERVER-28868 Set noCursorTimeout option on cursor in checkOplogs(). (cherry picked from commit ba040d4d48acda02caa4c6fe05da94f2ec5ef238) Branch: v3.4 https://github.com/mongodb/mongo/commit/11c69e72cee75ca7450785943866659c49656548 xgen-internal-githook commented on Thu, 20 Apr 2017 20:43:56 +0000: Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'} Message: SERVER-28868 Set noCursorTimeout option on cursor in checkOplogs(). Branch: master https://github.com/mongodb/mongo/commit/ba040d4d48acda02caa4c6fe05da94f2ec5ef238

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...