[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: |
|
||||||||||||||||
| 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 Cheers! -Brian |