-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding
The atClusterTime selection algorithm designed for the Global Point in Time reads project uses the last majority committed opTime timestamps from each targeted shard to select an atClusterTime timestamp. This is incompatible with the speculative snapshot optimization and can lead to problems on shards with enableMajorityReadConcern=false, so instead the algorithm should use the last applied opTime timestamps of the targeted shards.
- duplicates
-
SERVER-36312 Re-enable atClusterTime selection algorithm on mongos
- Closed
- has to be done after
-
SERVER-36312 Re-enable atClusterTime selection algorithm on mongos
- Closed
- is related to
-
SERVER-38041 Test single shard transactions with arbiters and enableMajorityReadConcern:false replica sets with lag
- Closed