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

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • Fully Compatible
    • Execution Team 2019-10-21, Execution Team 2019-11-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Gregory Wlodarek
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: