-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
errors encountered during a restore don't give context to what file/collection/index/etc is being operated on when the error is triggered. For example, I tried putting a corrupt BSON file into the dump directory, and the log output is:
2014-11-30T14:11:07.470-0500 building a list of dbs and collections to restore from dump dir 2014-11-30T14:11:07.477-0500 reading metadata file from dump/mci_dev/tasks.metadata.json 2014-11-30T14:11:07.478-0500 reading metadata file from dump/mci_dev/builds.metadata.json 2014-11-30T14:11:07.478-0500 reading metadata file from dump/mci_dev/patches.metadata.json 2014-11-30T14:11:07.478-0500 reading metadata file from dump/mci_dev/versions.metadata.json 2014-11-30T14:11:07.478-0500 restoring mci_dev.patches from file dump/mci_dev/patches.bson 2014-11-30T14:11:07.478-0500 restoring mci_dev.versions from file dump/mci_dev/versions.bson 2014-11-30T14:11:07.478-0500 restoring mci_dev.builds from file dump/mci_dev/builds.bson 2014-11-30T14:11:07.479-0500 restoring mci_dev.tasks from file dump/mci_dev/tasks.bson restore error: Invalid BSONSize: 1735027571 bytes
The log output should indicate which file triggered the error.