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

Reconstructing prepared transactions containing multi-key writes crashes the initial syncing node.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.1, 4.7.0
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Repl 2020-08-24
    • Linked BF Score:
      14

      Description

      On-disk catalog multi-key update for multi-statement transactions happens in a side transaction block. SERVER-48010 replaced ghost timestamp (determined by logical clock) with no-op write for timestamping the on-disk catalog writes on primaries. Since initial sync doesn't set transaction recoveryPrepareOpTime while reconstructing prepared transactions, it wrongly calls primary no-op write code path to acquire timestamp for the catalog write. As a result, we hit this invariant failure which leads to initial syncing node server crash.

      This happens in both 4.4 and master.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              suganthi.mani Suganthi Mani
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: