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

"Didn't find RecordId in WiredTigerRecordStore" on collections after an idle period

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Fixed
    • 3.0.0
    • 3.0.1, 3.1.0
    • WiredTiger
    • Fully Compatible
    • ALL
    • Hide

      No self-contained repro has been found. This bug has only been observed on complex systems. In particular, workloads that continually update collections will not hit this problem: only workloads where collections are idle for a period, then updated can trigger this bug,

      Show
      No self-contained repro has been found. This bug has only been observed on complex systems. In particular, workloads that continually update collections will not hit this problem: only workloads where collections are idle for a period, then updated can trigger this bug,

    Description

      A bug in an internal WiredTiger thread could cause corruption in collections that become idle, then are later updated again.

      A WiredTiger thread that discards old collections in cache could (under rare circumstances) start discarding a collection but give up part way through, leaving an incomplete tree in cache. If that collection was subsequently updated, the on-disk tree could become corrupted. A repairDatabase operation may be required to salvage data.

      Attachments

        1. Log_To_Upload
          5 kB
        2. serverStatus() command
          22 kB

        Issue Links

          Activity

            People

              michael.cahill@mongodb.com Michael Cahill
              michael.cahill@mongodb.com Michael Cahill
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: