Clean up transaction error codes

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-05-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Matthew Russotto
              Reporter:
              Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: