-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Correctness
-
ALL
-
200
Original slack thread: https://mongodb.slack.com/archives/C07T35KELLC/p1738125749813369
Max:
looks like the hang analyzer taking core dumps is filling up 100GB in
https://jira.mongodb.org/browse/BF-36363
. From the system logs in
, I see the total virtual memory used by all 24 mongod processes is 99GB. The resident memory is less than 5GB. I feel like one avenue would be to investigate what allocated memory within the mongod process because the WT cache is still restricted to 1GB. This is maybe better performed by the Server team so I'll tag
as well
For the Correctness team, I think
needs to be looked into for why it is ineffective at preventing the disk from filling up with core dumpsFor the future, I think the Correctness team can also consider using a named pipe so the contents of the
gcore
command can be piped into gzip/pgzip since the compressed size of the core dumps will be much smaller