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

RestartCatalogCommand can attempt to reinitialize oplog pointers on standalones

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 4.0.0, 4.1.1
    • Fix Version/s: 4.0.1, 4.1.2
    • Component/s: Storage
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Storage NYC 2018-07-30
    • Linked BF Score:
      45

      Description

      SERVER-34211 added code to guard against closeAll throwing an exception and potentially leaving the oplog pointer uninitialized.

      However, this code can be triggered on standalones, hitting the invariant that the oplog collection exists.

      As for the suggested fix, I've talked with Kyle Suarez and we believe the guard from SERVER-34211 is no longer necessary and can be removed. Specifically,
      SERVER-35671 moved the uassert such that if its triggered, the catalog is left in a consistent state.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: