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

ShardingDataTransformCumulativeMetrics Does Not Report Oldest Operation's Elapsed Time

    • Cluster Scalability
    • ALL
    • 2

      We currently document a serverStatus field shardingStatistics.resharding.totalOperationTimeElapsedMillis, however this field was never actually reported by the old metrics implementation as of 6.0 and is also not reported by the new implementation which we started using in 6.1.

      The oldest running resharding operation's elapsed time in milliseconds should be reported in the output of serverStatus as shardingStatistics.resharding.oldestActive.totalOperationTimeElapsedMillis.

      Consider also adding a counter for the elapsed time for the most recent successful operation, to ease tracking resharding performance in atlas based on historical serverStatus data.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            brett.nawrocki@mongodb.com Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: