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

Write $currentOp Metrics for Resharding at End of Operation

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding NYC

      Currently, resharding tracks metrics via ReshardingMetrics reported in $currentOp and ReshardingCumulativeMetrics (via its base class) reported in serverStatus. Because the serverStatus command returns metrics from the whole host in aggregate, it's difficult to capture metrics that are specific to a particular operation. As such, there are some metrics (e.g. duration spent in each phase) that are only reported by $currentOp. However, $currentOp is only available while the operation is still running, which limits its usefulness when trying to do analysis after the fact. Therefore, we should log the BSON object returned by reportForCurrentOp() at the end of the resharding operation.

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            brett.nawrocki@mongodb.com Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: