Fatal error when restoring a sharded cluster from snapshots

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      Ubuntu 18.04.6 LTS
      XSF
      Kernel - 5.4.0-1088-aws #96~18.04.1-Ubuntu SMP Mon Oct 17 02:57:48 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
      Disable Transparent Huge disabled
      AWS m6i.4xlarge
      SSD GP3 450 Gb
    • ALL
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      After upgrading to MongoDB 8 we have a problem restoring a sharded cluster from snapshots using this article.

      How we make snapshots:
      1. On each shard (including the config shard) on a secondary replica we execute this command db.fsyncLock()
      2. We take a snapshot using aws cli by executing this command aws ec2 create-snapshot ...other arguments...
      3. On each shard (including the config shard) secondary replica we execute this command db.fsyncUnlock()

      The problem arises when we do item 6 (in C. Restore Config Server Replica Set) - Restart the mongod as a new single-node replica set
      We get an error (you can see it in the attached log file) that causes the mongod process to crash.

        1. log.txt
          133 kB

            Assignee:
            Kenan Ali
            Reporter:
            Vladimir Belyakov
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: