[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:
Related
is related to SERVER-37349 Subsequent statements in a transactio... Closed
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: SERVER-37350 Shards should reject writes in snapshot sharded transactions to chunks that have moved
Branch: master
https://github.com/mongodb/mongo/commit/3cdf605c16901f98472bdce6e0fc779d2d213ddb

Generated at Thu Feb 08 04:45:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.