We have a 3.2.13 Mongodb replica set with WiredTiger on AWS.

We are observing a strange behaviour: when stopping and starting the mongod service, the start time is about 10 minutes, but when stopping the mongod service, then replicating the data disk to a new AWS instance, and restarting on that machine, the start time is about 2 hours.

What may be the cause for this?

  • Have you checked mongod.log file? What it says during that startup? tail -f /var/log/mongodb/mongod.log
    – JJussi
    Jan 3, 2018 at 14:46
  • @JJussi it doesn't show anything after printing 'options' and 'wiredtiger_open config'. Jan 4, 2018 at 13:18

1 Answer 1


It looks like the initial slowness is because the EBS volume (which is restored from snapshot) is being initialized during the service startup.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.