[SERVER-5173] Track replication getMores separately from client getMores. Created: 02/Mar/12  Updated: 06/Dec/22  Resolved: 27/Jan/20

Status: Closed
Project: Core Server
Component/s: Diagnostics, Replication
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Richard Kreuter (Inactive) Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: metrics, stats
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-44711 Add statistics metrics.repl.network.o... Closed
Related
is related to SERVER-5828 Metric/Stats Tracking Closed
Assigned Teams:
Replication
Participants:

 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.


Generated at Thu Feb 08 03:08:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.