-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-08-27, Sharding 2018-09-10, Sharding 2018-09-24, Sharding 2018-10-08
Currently, mongos aborts transactions by sending abortTransaction to all shards, since this was sufficient for the single shard case. Instead, it should be changed to only target the shards in the participant list that have been successfully sent startTransaction=true.
Mongos should also remember if a txnId (lsid/txnNumber pair) is aborted, so it won't accept more statements for a transaction after it chooses to abort.
- has to be done before
-
SERVER-37210 Mongos should implicitly abort on errors in a transaction that cannot be retried
- Closed
- is depended on by
-
DRIVERS-522 Support mongos pinning for sharded transactions
- Development Complete