Track replication getMores separately from client getMores.

XMLWordPrintableJSON

    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Richard Kreuter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: