[SERVER-20871] There should be a rather clear way to check the repair's progress Created: 12/Oct/15  Updated: 17/Apr/19  Resolved: 17/Apr/19

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Brian Lane
Resolution: Done Votes: 1
Labels: repairDatabase
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to TOOLS-938 The "mongodump --repair" command shou... Closed
is related to WT-6771 The log should clarify what the figur... Closed
is related to SERVER-24618 Progress update in currentOp for repa... Closed
Participants:

 Description   

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).



 Comments   
Comment by Brian Lane [ 17/Apr/19 ]

Thanks, dmitry.ryabtsev - I will resolve this one as gone away and we can consider SERVER-40662.

Cheers!

-Brian

Generated at Thu Feb 08 03:55:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.