[SERVER-76441] Include pps_allowance_exceeded in serverstatus Created: 22/Apr/23 Updated: 24/Jan/24 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kelsey Schubert | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Backport Requested: |
v7.3
|
||||||||||||
| Sprint: | Service Arch 2023-08-07, Service Arch 2023-08-21, Service Arch 2023-09-04, Service Arch 2023-09-18, Service Arch 2023-10-02 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
On environments that produce stats that include pps_allowance_exceeded in the output of the following command
capture it in serverStatus and ensure that it is included in FTDC. We should also review the output of this command and include other metrics that we believe would be helpful diagnosing network issues. cc cailin.nelson@mongodb.com, nikki.sloan@mongodb.com |
| Comments |
| Comment by Cailin Nelson [ 22/Apr/23 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note: Azure also has some similar statistics, see Application Usage on https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-how-it-works. At least the vf_tx_dropped might be interesting? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 22/Apr/23 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Requesting backports for consideration, but we should be careful to stage them (e.g. make sure it's released to 7.0 before backporting to 6.0). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kelsey Schubert [ 22/Apr/23 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This stat exists on AWS. In Azure you can run the tool but these stats are not available. GCP does not return any stats with ethtool. Sample output on AWS (run from a spawnhost in evergreen that I spun up for this purpose so it's pretty boring):
|