FCBIS will never delete drop-pending tables

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 6.0.4, 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
    • None

      This is the same class of problem as SERVER-72422.

      On startup, we start a "timestamp monitor" on the StorageEngine, which is responsible for completing the second phase of the two-phase drop we employ to drop collections and indexes.

      After completing a FCBIS, we do not start the timestamp monitor again after re-constructing the storage engine. As a result, we will never actually drop any collections or indexes from the storage engine. This can be fixed permanently by restarting the server.

              Assignee:
              Matthew Russotto
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: