Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
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?
It looks like the initial slowness is because the EBS volume (which is restored from snapshot) is being initialized during the service startup.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html
tail -f /var/log/mongodb/mongod.log– JJussi Jan 3 '18 at 14:46