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

FCBIS may never truncate the oplog

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 5.2.0, 6.0.0, 6.1.0, 6.2.0-rc4
    • 6.0.4, 6.2.0-rc5, 6.3.0-rc0
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v6.2, v6.0
    • Repl 2023-01-09

    Description

      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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-72423 FCBIS will never delete drop-pending tables

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Engineering Test - For adding, improving or fixing bugs in eng test suites SERVER-72525 Randomly choose between FCBIS and logical initial sync every time in our testing

          • Major - P3 - Major loss of function.
          • Open

          Activity

            People

              matthew.russotto@mongodb.com Matthew Russotto
              louis.williams@mongodb.com Louis Williams
              Votes:
              1 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: