-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: None
-
Component/s: None
-
3
-
Tools and Replicator
-
0
-
Needed
If mongorestore is interrupted it can leave collections in a weird state. In some cases, timeseries from 5.2 - 7.x, the collection can be left in an unusable state if oplog replay is interrupted. For other collections, the data can be inconsistent and not reflect any specific point in the collection's history.
Mongorestore should attempt to clean up collections it creates (drop them) whenever it is interrupted. This is a best effort attempt, since we cannot catch all cases where we are interrupted (SIGKILL). But we can catch at least the following:
- SIGTERM
- SIGINT (Ctrl-C)
- Server returns an error during restore