[SERVER-37210] Mongos should implicitly abort on errors in a transaction that cannot be retried Created: 19/Sep/18  Updated: 29/Oct/23  Resolved: 09/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:RouterSupport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-36589 Implement mongos abort logic Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-10-08, Sharding 2018-10-22
Participants:

 Description   

If mongos receives an error in a transaction that it cannot continue on (either because the error is not retryable or it has exhausted its allowed retry attempts), it should implicitly abort the in-progress transaction. This should include sending abort to all contacted participant shards and transitioning to an aborted state.



 Comments   
Comment by Githook User [ 09/Oct/18 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-37210 Mongos should implicitly abort transactions on unhandled errors
Branch: master
https://github.com/mongodb/mongo/commit/d2d7dbadcc008a484218321666aae44b75964787

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