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

POC: Constant transaction number per participant

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29

      There is a one-to-one mapping between the txnNumber and a transaction participant / retryable write (no transaction). We should make a participant only know of its constant transaction number. Bumping txnNumber will try to abort the current participant, which throws an exception if it can't, and start a new one. As a result, participant only needs to check its state (aborted or not) and should never know of the change of the transaction number.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: