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?
tail -f /var/log/mongodb/mongod.log
– JJussi Jan 3 '18 at 14:46