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

Add marker file for journaling to ensure a clean restart

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Won't Fix
    • None
    • None
    • MMAPv1, Stability, Storage
    • None
    • Storage Execution
    • ALL

    Description

      When the journal files are wiped/truncated, like during fsync+lock, a marker file should be written so if a backup is made, or the server crashes, the server can automatically restart instead of complaining about a lock file but no journal files.

      There are many cases where this happens, like dropDatabase, moveChunk, and repair.

      This may be MMapV1 specific.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19778 Mongod recovery fails after power cycle, mmap storage, no journal files present

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-8358 "Move chunk commit failed" shutdown leaves mongod with no journal files and mongod.lock file

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19707 A crash after dropDatabase leaves the server unable to restart

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              scotthernandez Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: