Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-57760

Introduce dedicated OpCounters-like metrics for resharding and use them in ReshardingOplogApplier

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.4, 5.1.0-rc0
    • Sharding
    • None
    • Fully Compatible
    • v5.0
    • Sharding 2021-07-12
    • 1

    Description

      ReshardingOplogApplier currently increments globalOpCounters when applying inserts, updates, and deletes. Using globalOpCounters can make it difficult to distinguish in the FTDC/t2 output the ops/sec from the client workload from the ops/sec from resharding as it tries to keep up with the client writes.

      Having a new shardingStatistics.resharding.opcounters subsection would enable splitting up these metrics in ReshardingOplogApplier from the globalOpCounters.

      shardingStatistics:
        ... (other existing metrics) ...
        resharding:
          ... (other existing metrics) ...
          opcounters:
            insert: int64
            update: int64
            delete: int64
      

      Attachments

        Issue Links

          Activity

            People

              haley.connelly@mongodb.com Haley Connelly
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: