[SERVER-59633] Capture device mapper disk statistics in FTDC Created: 26/Aug/21 Updated: 01/Nov/23 Resolved: 01/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Arhelger | Assignee: | Brad Moore |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Security 2023-10-16, Security 2023-10-30, Security 2023-11-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In some cases, a databases dbpath may be back by mdraid or lvm. In these cases the device mapper may exhibit very different queueing behavior compared to the underlying physical disks. Since there could be hundreds of dm devices, omitting all but those actually involved in the function of the process could be excluded (see SERVER-59615 for an example of how to find this mapping). |
| Comments |
| Comment by Githook User [ 23/Oct/23 ] |
|
Author: {'name': 'W. Brad Moore', 'email': 'brad.moore@mongodb.com', 'username': 'wbradmoore'}Message: |
| Comment by Bruce Lucas (Inactive) [ 03/Sep/21 ] |
|
We need more details to assess the impact on run-time performance number of metrics in FTDC (and therefore FTDC retention, as well as usability). |
| Comment by Edwin Zhou [ 03/Sep/21 ] |
|
bruce.lucas, do you have any input here? |