[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: |
|
||||||||||||||||
| 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. |