-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Repl 2025-09-29
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We should have a way to track and understand the shape of what's happening in the server with regards to changes to be applied to the customer's data and the documents targeted to guide future investments, such as SERVER-110070. While SERVER-110070 is specifically about oplog application on the secondary, knowing the "flavor" of queries running on both primary and secondary may guide useful investments. Some ideas:
- number of reads and writes
- number of indexes written per logical write
- number of docdiff vs other types
- is depended on by
-
SERVER-110070 Merge update queries on secondaries when history is not required
-
- Blocked
-
- is related to
-
-
- Blocked
-
- related to
-
SERVER-111305 Investigate metrics that would be useful to guide replag solutions on secondaries
-
- Backlog
-