-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-11-05
Currently, the multi-versioned routing table is only used when selecting a global read timestamp, to verify that the set of shards used to compute the read timestamp matches the set that would be targeted at that timestamp. Now that mongos supports multi statement transactions, subsequent statements should route their requests using the multi-versioned routing table corresponding to the already selected read timestamp.
- is depended on by
-
SERVER-37045 Consider not allowing killCursors to start a cross-shard transaction
- Closed
- related to
-
SERVER-37350 Shards should reject writes in a transaction for chunks they no longer own
- Closed