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

Investigate changes in SERVER-43815: Validate cmd should report MB of I/O per second in curOp so that users can make more informed use of throttling via the 'maxValidateMBperSec' server parameter

XMLWordPrintableJSON

      Description

      Downstream Change Summary

      Two new fields added to CurOp. 'dataThroughputAverage' and 'dataThroughputLastSecond'. These are only shown in CurOp when running validate() in either foreground or background. They show the data throughput during the duration of the validate command.

      Description of Linked Ticket

      We already have the DataThrottle class that together with the ThrottleCursors used in collection validate enforce 'maxValidateMBperSec' per validate cmd.

      We could add something to keep track of MB/sec in general to DataThrottle; then we'd need to attach the information regularly to the curOp output.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 51 weeks, 1 day ago