-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Logging
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently there is no good way to check the repair's progress, which easily takes hours for reasonably large databases.
While it is possible to get an idea of the progress by monitoring the data files allocations (the only thing mongod reports during the repair), it is quite inconvenient and rough indicator.
We should print at least a number of bytes written or a number of documents written out of total (e.g. taken from the collection stats).
- is related to
-
TOOLS-938 The "mongodump --repair" command should have a clear progress indicator
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-