-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.0.0
-
Component/s: Sharding
-
ALL
-
As SERVER-31887 pointed out, a failed command advances the cluster time but not the operation time. If we perform a secondary read right after the failed command, the operation time being returned is actually the cluster time. It's problematic because there is no oplog entry at the operation time being returned.
- duplicates
-
SERVER-35377 Operations on new clients get latest in-memory clusterTime as operationTime
- Closed
- is related to
-
SERVER-34866 Blacklist/unblacklist tests in secondary_reads_passthrough suite
- Closed
-
SERVER-32883 Enhanced FSM testing for reading from secondaries
- Closed
- related to
-
SERVER-31887 clusterTime advanced on primary without anything being written to oplog
- Closed
-
SERVER-43470 Complete TODO listed in SERVER-35156
- Closed