[SERVER-28694] operation_time_read_and_write_concern.js should use awaitLastOpCommitted after re-enabling replication Created: 07/Apr/17  Updated: 06/Dec/17  Resolved: 07/Apr/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5.6

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 07/Apr/17 ]

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

Generated at Thu Feb 08 04:18:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.