[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 Created: 23/Oct/19 Updated: 13/Nov/23 Due: 01/May/20 Resolved: 04/May/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 40 weeks, 2 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream 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 TicketWe 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 changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 04/May/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |