[SERVER-24618] Progress update in currentOp for repairDatabase Created: 16/Jun/16 Updated: 06/Dec/22 Resolved: 05/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng, repairDatabase | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
When running repairDatabase / compact the only way of observing progress is looking at the log files. Index builds provide a nice message of progress in the currentOp output, which I believe repair/compact could similarly provide. |
| Comments |
| Comment by Eric Milkie [ 05/Aug/19 ] |
|
We don't currently have a good way of reporting percentage-complete progress, although we do now log general progress when repair and compact run in the system log. |