-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.3.9
-
Component/s: Replication, Sharding
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Sprint:Sharding 16 (06/24/16)
-
Linked BF Score:0
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.
- is related to
-
SERVER-21861 Better Timestamp object comparison in mongo shell
-
- Closed
-