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

Measure latency/throughput of inserting a batch in ReshardingCollectionCloner::doOneBatch

    XMLWordPrintableJSON

Details

    • Sharding NYC
    • v5.0

    Description

      • Should collect latency information as a histogram with coarse grained buckets (0-10ms,11-100ms,101-1000ms, 1001-10000ms, 10001+ms)
      • Should track total number of invocations that complete
      • Should report these metrics in serverStatus to be consumed by FTDC.
      • Should report these metrics in currentOp if there is a resharding operation currently in progress.

      https://github.com/mongodb/mongo/blob/6659e192ee5feceda14bebe1cb22f219d5d765fd/src/mongo/db/s/resharding/resharding_collection_cloner.cpp#L303

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-57742 Create a non-specialized version of the OperationLatencyHistogram class

          • Major - P3 - Major loss of function.
          • Closed
          duplicates

          New Feature - A new feature of the product, which has yet to be developed. SERVER-64388 Track and Report New Recipient Latency Fields in ServerStatus

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding-nyc Backlog - Sharding NYC
              lamont.nelson@mongodb.com Lamont Nelson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: