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

Must invalidate all sessions on step down

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.10, 4.4.1, 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Repl 2020-05-18, Repl 2020-06-01, Repl 2020-08-10
    • Linked BF Score:
      26

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: