Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.4
Affects Version/s: None
Component/s: Sharding
Labels:
- ShardedTxn:RouterSupport

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-08-27, Sharding 2018-09-10, Sharding 2018-09-24, Sharding 2018-10-08
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Randolph Tan
Reporter:: Jack Mulrow
Participants:: Githook User, Jack Mulrow, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Aug 10 2018 04:01:37 PM UTC
Updated:: Oct 29 2023 10:29:03 PM UTC
Resolved:: Sep 26 2018 02:41:35 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates