Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-8860

EBS volumes should be initialised after creating from the snapshot before starting the {{mongod}} process

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Atlas, ecosystem
    • Labels:

      As per the AWS docs:
      Initializing Amazon EBS Volumes,

      For a new volume created from a snapshot, you should read all the blocks that have data before using the volume.

      If the volumes are not initialised, it may take several minutes to several hours for the mongod instance to start.

      This generally affects MongoDB 3.2 with WiredTiger which samples the oplog while starting (see SERVER-19551). However, it should be better to have the volume initialised in all versions as the data anyways has to be read from disk and the process will be slow for uninitialised volumes.

      Information regarding this behaviour should be good to have in either of these MongoDB docs:

      Related tickets:

      Help: https://jira.mongodb.org/browse/HELP-2705

            Assignee:
            Unassigned Unassigned
            Reporter:
            ankur.raina@mongodb.com Ankur Raina (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              13 weeks, 2 days ago