Operational Defect Database

BugZero found this defect 2516 days ago.

MongoDB | 372129

[SERVER-28694] operation_time_read_and_write_concern.js should use awaitLastOpCommitted after re-enabling replication

Last update date:

12/6/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.5.6

Description:

Info

operation_time_read_and_write_concern.js disables replication to secondaries using a failpoint, makes a local write to the primary, re-enables replication, then waits for the write to replicate to the secondaries before issuing a read with readConcern majority, expecting the locally written document to be returned. Currently the test uses ReplTest.awaitReplication, which blocks until the secondaries last applied optime matches the primary's, but it should use ReplTest.awaitLastOpCommitted, which blocks until their last committed optime is caught up. This will ensure the majority read returns the expected documents.

Top User Comments

xgen-internal-githook commented on Fri, 7 Apr 2017 21:46:24 +0000: Author: {u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'} Message: SERVER-28694 operation_time_read_and_write_concern.js should use awaitLastOpCommitted after re-enabling replication Branch: master https://github.com/mongodb/mongo/commit/dd4b747f9b740b91730aeaa1ca77270c8382734a

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:

...