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

WiredTiger unable to start if crash leaves 0-length WiredTiger file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.2, 3.1.1
    • Component/s: WiredTiger
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:

      Description

      A crash can leave the WiredTiger.basecfg file existing but empty, and in that case WiredTiger won't start. The file should be fsync'ed after being created.

        Attachments

          Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. WT-1901 Issues resolved in WiredTiger 2.5.3

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17451 WiredTiger unable to start if crash leaves 0-length journal file

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17152 WiredTiger file corrupted during power cycle test

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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: