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

Invariant failure, WT_NOTFOUND: item not found

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical - P2
    • Resolution: Done
    • 4.4.0, 4.4.1
    • None
    • Stability, WiredTiger
    • None
    • ALL
    • Hide

      Unfortunately I cannot get it reproduced on will yet.

      Show
      Unfortunately I cannot get it reproduced on will yet.
    • 119

    Description

      Hi

       

      We have been getting infrequent (1-2 times a day) aborts of this kind lately. This happened on 4.4.1 and 4.4.0 too. We have had years without issue (3-node replica set), upgrading as new versions come around. It isn't tied to specific times either.

      This is on an AWS I3 instance with nvme drive, formatted to xfs.

      Snippet of the logs here and in the attachement.

      https://pastebin.com/uqauh8H0

      We have tried removing the DB path and resyncing from a secondary, but this did not fix it.

      What could cause this? Could it be a specific query? Could the disk itself be corrupt? How can I help pinpointing the issue?

      Attachments

        1. image-2020-10-15-16-49-06-849.png
          image-2020-10-15-16-49-06-849.png
          69 kB
        2. MongoDB Abort.json
          22 kB
        3. mongo-log.json
          10 kB

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-50880 Mongod Server Failed with signal 6

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

          Question - SERVER-51386 Mongo 4.4.1 Crashes often

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

          Bug - A problem which impairs or prevents the functions of the product. WT-6811 Allow older readers to read behind a mixed-mode operation

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

          Task - A task that needs to be done. WT-6928 Removing historical updates required by the old reader session

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

          Question - SERVER-52530 Mongo v.4.4.1 crash - UnknownError -31803: WT_NOTFOUND

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

          Activity

            People

              jonathan.streets@mongodb.com Jonathan Streets (Inactive)
              pieterwjordaanpc@gmail.com Pieter Jordaan
              Votes:
              1 Vote for this issue
              Watchers:
              30 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: