[SERVER-41287] Add count of instances when flow control is engaged Created: 23/May/19 Updated: 29/Oct/23 Resolved: 06/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc1, 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | Execution Team 2019-06-17 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
It will be useful for identifying mongod instances where flow control has been engaged to have cumulative metrics about the number of times flow control has been engaged on a mongod instance since startup, and the cumulative time for which flow control has been engaged. For the purposes of this ticket, flow control being "engaged" means the isLagged metric is 1, i.e., the current majority committed lag is greater than some established threshold percentage of the configured target maximum lag. These new metrics would be based on the isLagged metric, so maybe these could be named
|
| Comments |
| Comment by Githook User [ 06/Jun/19 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: (cherry picked from commit c27cafcd34190924cd62267fa8b42baf3caa69cb) |
| Comment by Githook User [ 06/Jun/19 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: |