-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-11-10
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There are some statistics that would be very helpful to do a dry run of a mongotune policy, and to set up a dashboard that will help us to determine the success of the track. Among these stats we have:
- Report statistics for maxQueueLength, loadShed tasks and number of admissions wasted per priority.
- Report all operations that would be chosen to be deprioritized even if the de-prioritization would be disabled (it could be called totalChosenToDeprioritize or something similar).
- Have two new objects in the queue.execution.read and write objects in server status: shortRunning and longRunning, which would report statistics similar to normalPriority and lowPriority, but, they actually refer to total running time of the operation, total queued time, cpu usage, etc. To determine what a longRunning operation is, use the same heuristic we're currently using to de-prioritize, and materialize these stats at the operation end.
The purpose of this ticket is to add those statistics to serverStatus.
- is duplicated by
-
SERVER-113075 Count the number of admissions wasted
-
- Closed
-