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

Missing or corrupt data files should cause MongoDB to exit with an error message to run repair

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.3, 4.1.2
    • Component/s: None
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Epic Link:
    • Sprint:
      Storage NYC 2018-07-16, Storage NYC 2018-07-30

      Description

      In any of the following cases during startup, MongoDB should exit with the same error message requiring the user to run --repair. The current behavior is a crash with no helpful information.

      • Missing or corrupt _mdb_catalog
      • Missing or corrupt WiredTiger.wt metadata
      • Missing or corrupt collections or indexes

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: