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

Ensure config.transactions and TransactionParticipant have consistent state after every command

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      We require that config.transactions and TransactionParticipant have consistent state after every command (or the session is invalidated) so that subsequent users of TransactionParticipant know whether the session needs to be reloaded from disk. We will always update config.transactions before updating the in-memory state in TransactionParticipant. If we throw an exception before updating the in-memory state, we must invalidate the session. Audit all abort, commit, and prepare codepaths to ensure they follow this pattern

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: