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

WiredTiger metadata corruption detected - unable to repair

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.18
    • Component/s: None
    • Labels:
      None
    • ALL

      Hi all,

      We are using Graylog, Elasticsearch and MongoDB for logging and archiving. These apps are run as docker containers with 3 replicas on 3 RHEL servers. We are using MongoDB version 3.6.18
      Generally, the docker containers goes down and they are automatically brought up by the docker daemon. But sometimes, the shutdown is not proper and the data in MongoDB gets corrupted. Till now, we used to perform a repair and the data was able to be recovered successfully.

      I had previously created a ticket for the similar issue (https://jira.mongodb.org/browse/SERVER-61936). At that time, I had restored the data from the backup and could not try the repair command as mentioned by "Edwin Zhou".

      I have encountered the problem again. The same DB got corrupted.
      I have tried the repair operations with 4 different versions of MongoDB. All the log outputs from the repair operations are attached below. But none of the repair was successful.

      I have attached the WiredTiger files from this corrupted db.

      Can you please help me in recovering from this failure?
      Also can you let me know how I can prevent this frequent corruption of Data in the DB?

      Thanks,
      Saroj

        1. Repair - 3.6.18.txt
          4 kB
        2. Repair - 3.6.23.txt
          4 kB
        3. Repair - 4.4.13.txt
          4 kB
        4. Repair - 4.4.3.txt
          4 kB
        5. WiredTiger
          0.0 kB
        6. WiredTiger.turtle
          1 kB
        7. WiredTiger.wt
          640 kB
        8. WiredTigerLAS.wt
          4 kB

            Assignee:
            edwin.zhou@mongodb.com Edwin Zhou
            Reporter:
            saroj.jillalla@cgi.com Sarojini Jillalla
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: