[SERVER-63675] Track usedDisk in serverStatus Created: 15/Feb/22 Updated: 10/Mar/23 |
|
| Status: | Investigating |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.2.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Arhelger | Assignee: | Chris Harris |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | diagnostics | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
This request is for two query related counters in Server Status. These names are just suggestions. usedDisk: Incremented when queries or aggregations wrote data to temporary files. |
| Comments |
| Comment by Kevin Arhelger [ 15/Feb/22 ] |
|
I would find it helpful to have a breakout of read and write operations and bytes written / read as these operations progress. That should provide a more complete picture of IO activity for a given mongodb instance. Per operation io statistics for tmp would also be helpful in the slow query message and profiler. |
| Comment by Bruce Lucas (Inactive) [ 15/Feb/22 ] |
|
I wonder if it would be also be helpful to have a field that tracks the amount of disk used. Ideally for such a metric to be useful I think it would need to track the usage as the query is running, so that it doesn't show up as just a large bump at the end of a long-running query, making it hard to correlate with system disk usage metrics. |