Details
-
Task
-
Resolution: Done
-
Major - P3
-
mongodb-3.2
-
None
Description
The documentation page for backing up a sharded cluster contains a section on how to lock config server replicaset's secondary in order to get a consistent metadata snapshot.
The section requests to search for a 'moveChunk.commit' message, which will work most of the time, but in the case of failed migrations it might not.
A more appropriate instructions would be to run the same query:
use config;
|
db.changelog.find({what:/^moveChunk/}).sort({time:-1}).next()
|
And make sure that the last moveChunk.start entry has a corresponding moveChunk.commit or moveChunk.from entry, which would indicate that the latest migration has completed (whether successfully or not).