Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34011

Concurrency between transaction and other threads that can abort transaction

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-04-09
    • 55

      Due to migration, killSession and other implicit transaction abort, multi-statement transaction functions need to consider the concurrency even if the session has been checked out.

      If a high txnNumber is received from migration, the current transaction needs to abort. (SERVER-33432)
      If migration has the same txnNumber, the current transaction must be in state None (retryable writes).
      All accesses to the transaction functions must check the txnNumber and the state at the beginning.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: