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

Must invalidate all sessions on step down

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.1, 4.7.0, 4.2.10
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2020-05-18, Repl 2020-06-01, Repl 2020-08-10
    • 26

      If we abort a transaction on a primary, we may never have written anything durably about it. If we step down, we must forget about all aspects of this transaction, including the transaction number (which may be re-used on the new primary). This means we must not just abort transactions in progress, but also invalidate all sessions, on stepdown.

      We should also invariant in beginOrContinueTransactionUnconditionally, when we are attempting to start the same transaction number as already exists on the participant, but that transaction number is not in progress.

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            matthew.russotto@mongodb.com Matthew Russotto
            0 Vote for this issue
            11 Start watching this issue