[SERVER-54770] Add /proc/meminfo MemAvailable to FTDC Created: 24/Feb/21 Updated: 29/Oct/23 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | 4.9.0, 4.4.5, 4.0.24, 4.2.14 |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Kevin Arhelger | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||
| Sprint: | Security 2021-03-22 | ||||
| Participants: | |||||
| Description |
|
When analyzing low memory / out of memory situations, currently a manual calculation for available memory is needed. As the Linux page cache will attempt to consume all available memory, the MemFree statistic alone cannot be used to perform this analysis. Redhat 7 and later include a MemAvailable counter in /proc/meminfo https://www.kernel.org/doc/Documentation/filesystems/proc.txt
While a close approximation of MemAvailable can be made from simply summing MemFree + Cached + Buffers. I've found MemAvailable to be slightly more pessimistic and would be really helpful in providing a single metric for memory analysis. |
| Comments |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: (cherry picked from commit 0cde744f93ba588956d13fafa9cd74b0ded9334a) |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: (cherry picked from commit 0cde744f93ba588956d13fafa9cd74b0ded9334a) |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: (cherry picked from commit 0cde744f93ba588956d13fafa9cd74b0ded9334a) |
| Comment by Mark Benvenuto [ 10/Mar/21 ] |
|
Yes, I created the backports to 4.0, 4.2, and 4.4. I agree that we should not backport to 3.6. |
| Comment by Kevin Arhelger [ 10/Mar/21 ] |
|
Thank you mark.benvenuto for working on this. This will greatly enhance our ability to diagnose memory issues. Would it be possible to backport this to 4.0 and later? (With the imminent end of support for 3.6 I don't think its necessary for that version). |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |