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

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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.1, 4.7.0
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2020-08-24
    • 20

      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.

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

              Created:
              Updated:
              Resolved: