[SERVER-24628] ReplSetTest.awaitLastOpCommitted can fail to wait for the last op to be committed Created: 16/Jun/16  Updated: 25/Jan/17  Resolved: 20/Jun/16

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 3.3.9

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-21861 Better Timestamp object comparison in... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 16 (06/24/16)
Participants:
Linked BF Score: 0

 Description   

ReplSetTest.awaitLastOpCommitted depends on comparing Timestamps, but Timestamp comparison in the shell is broken (per SERVER-21861). This means that if the committed optime of two servers differs only in the increment portion of the Timestamp, we might return before all servers are actually caught up.



 Comments   
Comment by Githook User [ 20/Jun/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-24628 Do proper Timestamp comparison when waiting for last op to be committed
Branch: master
https://github.com/mongodb/mongo/commit/8d94d0fe220899083009fef8c6accfe1ea52c7ed

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