-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-10-22, Sharding 2018-11-05
Sharded transactions with snapshot read concern use a historical routing table to target requests to shards that owned chunks at the chosen global read timestamp. If a write is targeted to a shard that used to own a chunk, but no longer does, the write should fail even if there are no write conflicts.
- is related to
-
SERVER-37349 Subsequent statements in a transaction should target shards using the global read timestamp
- Closed