-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-05-07
When a transaction is aborted implicitly, we currently return different error codes due to different timing. When an operation is running and the transaction gets aborted, we return TransactionAborted, but if the transaction is aborted between operations, the next operation gets NoSuchTransaction. We'd like to unify them to be NoSuchTransaction. This will also be consistent with commands sent after failover, where the new primary expects startTransaction field and returns NoSuchTransaction.
- is related to
-
SERVER-34256 On error within a transaction, expose in response whether transaction can be safely retried from the beginning
- Closed