-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2019-05-20
-
21
Under heavy load, it is possible for abortTransaction to fail while checking out the session. In this case, we will get a LockTimeout (marked transient). The transaction has been aborted, so we can simply ignore this error.
The same code also fails to handle different errors for different shards, which can also happen. We can use the "raw" field to make sure each error is an allowable one.
- related to
-
SERVER-40757 Fix snapshot_read_kill_operations.js to handle read-only transactions that are aborted
- Closed