[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 Created: 03/Oct/19  Updated: 29/Oct/23  Resolved: 23/Oct/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-13165 Investigate changes in SERVER-43815: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-10-21, Execution Team 2019-11-04
Participants:

 Description   

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.



 Comments   
Comment by Gregory Wlodarek [ 30/Apr/20 ]

kay.kim looks like this was an oversight. It was intended to show up in the currentOp output. I filedĀ SERVER-47854 to fix this.

Comment by Githook User [ 23/Oct/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: 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
Branch: master
https://github.com/mongodb/mongo/commit/afcdf8a352a1b56cd150b8f373fa8a5b7786880b

Generated at Thu Feb 08 05:04:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.