Details
-
Improvement
-
Status: Closed
-
Minor - P4
-
Resolution: Duplicate
-
None
-
None
-
Replication
Description
It could be useful for monitoring-type applications if getMores on the oplog cursor were counted as a separate statistic. (The existing getMore counter could be left alone, and monitoring packages could just subtract the oplog getMores, say.)
Rationale: the number of getMores generated by replicating secondaries is non-determinstic, can be high, and are likely not to be distributed uniformly over a replica set.
Attachments
Issue Links
- duplicates
-
SERVER-44711 Add statistics metrics.repl.network.oplogGetMoresProcessed
-
- Closed
-
- is related to
-
SERVER-5828 Metric/Stats Tracking
-
- Closed
-