[SERVER-39966] Report both total actual system memory and cgroup memory limit in hostInfo Created: 05/Mar/19  Updated: 29/Oct/23  Resolved: 08/Mar/19

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Task Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Matt Lord (Inactive)
Resolution: Fixed Votes: 1
Labels: FTDC, memory
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-16571 Use Actual Memory Constraint vs. Tota... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

WIth SERVER-16571 hostInfo.memSizeMB will now report the cgroup memory limit instead of the actual system memory. However system memory statistics in ftdc are reported for the system as a whole, not just for the container, so interpreting them requires knowing the total actual system memory. There may be other diagnostic purposes for knowing the actual system memory as well, so it's difficult to know up front the impact of no longer having this information. Also, seeing different values for system memory vs memSizeMB will alert us to the fact that a cgroup is in use, which also has diagnostic value.

Suggest adding a field, maybe hostInfo.systemMemSizeMB, to report this information.



 Comments   
Comment by Matt Lord (Inactive) [ 08/Mar/19 ]

This was resolved as part of SERVER-16571:
Message: SERVER-16571 Use Actual Memory Constraint vs. Total System Memory When They Differ
Branch: master
https://github.com/mongodb/mongo/commit/fafe4d03edd877e4c022cb3dd714ab1ea6ae4fcd

Generated at Thu Feb 08 04:53:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.