-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.0.0
-
Component/s: None
-
None
When using the new tcmalloc allocator it's possible to have the following warnings in the log
{"t":{"$date":"2024-10-02T07:20:14.375+00:00"},"s":"W", "c":"CONTROL", "id":8640300, "ctx":"initandlisten","msg":"For customers running the tcmalloc-google memory allocator, we suggest setting the contents of sysfsFile to 'always'","attr":{"sysfsFile":"/sys/kernel/mm/transparent_hugepage/enabled","currentValue":"madvise"},"tags":["startupWarnings"]}
{"t":{"$date":"2024-10-02T07:20:14.375+00:00"},"s":"W", "c":"CONTROL", "id":8640301, "ctx":"initandlisten","msg":"For customers running the updated tcmalloc-google memory allocator, we suggest setting the contents of sysfsFile to 'defer+madvise'","attr":{"sysfsFile":"/sys/kernel/mm/transparent_hugepage/defrag","currentValue":"madvise"},"tags":["startupWarnings"]}
{"t":{"$date":"2024-10-02T07:20:14.375+00:00"},"s":"W", "c":"CONTROL", "id":8640302, "ctx":"initandlisten","msg":"We suggest setting the contents of sysfsFile to 0.","attr":{"sysfsFile":"/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none","currentValue":511},"tags":["startupWarnings"]}
Since some tools (e.g. mongosh) reports back only the msg field would be helpful to change these "msg" in order to give a more useful information to identify the issue.