FCBIS may never truncate the oplog

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 6.0.4, 6.2.0-rc5, 6.3.0-rc0
    • Affects Version/s: 5.2.0, 6.0.0, 6.1.0, 6.2.0-rc4
    • Component/s: None
    • Replication
    • Fully Compatible
    • ALL
    • v6.2, v6.0
    • Repl 2023-01-09
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      We install a callback inside the storage engine to determine how much oplog to keep for uncommitted transactions.

      Upon completion, FCBIS reconstructs a new storage engine, but it does not re-instantiate this callback. When this callback is not present, we default to not truncating the oplog.

      As a result, we will never truncate the oplog after completing a FCBIS. Restarting the node fixes this problem permanently.

            Assignee:
            Matthew Russotto
            Reporter:
            Louis Williams
            Votes:
            1 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated:
              Resolved: