[SERVER-37350] Shards should reject writes in a transaction for chunks they no longer own Created: 27/Sep/18 Updated: 29/Oct/23 Resolved: 30/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:GlobalSnapshot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-10-22, Sharding 2018-11-05 | ||||||||
| Participants: | |||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 30/Oct/18 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |