-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: Legacy C++ Implementation
-
Component/s: mongodump
As near as I can tell, if you run 'mongodump --oplog', and if the oplog has rolled over so that the entry at opLogStart is no longer present, 'mongodump' will not detect the problem, and will go ahead and create a backup that is missing the critical oplog entries
I'd suggest that 'mongodump' should check for this condition and error out if it happens.