-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2019-05-20
-
13
It turns out that for read-only transactions, it is allowable that one shard commit and one shard abort, as long as the client receives an error (since "committing" for a read-only transaction doesn't do anything except wait for the data read to be majority committed). In this case, a read-only transaction was interrupted, causing one shard to commit and the other to abort. The test should be fixed to handle this case.
- is related to
-
SERVER-40996 abortTransaction in cleanup_txns.js does not handle LockTimeout
- Closed
- related to
-
SERVER-38931 Apply relevant changes to snapshot_read_kill_operations.js to 4.0 branch
- Closed