Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15985

[SERVER] Investigate changes in SERVER-69954: ShardingDataTransformCumulativeMetrics Does Not Report Oldest Operation's Elapsed Time

    XMLWordPrintableJSON

Details

    Description

      Original Downstream Change Summary

      Please remove any mentions of totalOperationTimeElapsedMillis due to the work outlined in SERVER-69954. Removing the mention will make docs more accurate.

      Description of Linked Ticket

      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.

      Attachments

        Activity

          People

            joseph.dougherty@mongodb.com Joseph Dougherty
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              45 weeks, 5 days ago