[bitnami/mongodb] warns of vm.max_map_count and sysfsFile

[wilburfs]

Name and Version

bitnami/mongodb

What architecture are you using?

None

What steps will reproduce the bug?

mongosh connect to db

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

When I connect using mongosh, the db gives the following warning. Should I modify the corresponding configuration on the host machine or inside the pod?

-----------------------------
The server generated these startup warnings when booting
   2025-03-16T21:01:46.529+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
   2025-03-16T21:01:46.529+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
   2025-03-16T21:01:46.529+00:00: We suggest setting the contents of sysfsFile to 0.
   2025-03-16T21:01:46.529+00:00: vm.max_map_count is too low

Additional information

No response

[javsalgar]

Hi,

This kind of kernel settings should be done in the host running kubernetes.

[wilburfs]

@javsalgar hello javsalgar,
I set the env on the pod host : echo $GLIBC_TUNABLES to be glibc.pthread.rseq=0
and cat /etc/sysctl.conf to be ：

 _net.core.somaxconn = 4096
....
kernel.printk = 5
vm.max_map_count=262144_

then ,restart the pod, the warn shown again :

 _2025-03-17T10:04:38.630+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
   2025-03-17T10:04:38.630+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
   2025-03-17T10:04:38.630+00:00: We suggest setting the contents of sysfsFile to 0.
   2025-03-17T10:04:38.630+00:00: vm.max_map_count is too low_

[javsalgar]

Hi,

This /etc/sysctl.conf is in the host, right? Did you verify that the sysctl command is aplying the updated settings?

sysctl -p /etc/sysctl.conf

[wilburfs]

@javsalgar hello,
yes,
sysctl -p /etc/sysctl.conf
net.core.somaxconn = 4096
net.ipv4.tcp_max_tw_buckets = 4096
net.ipv4.tcp_slow_start_after_idle = 0
kernel.sysrq = 1
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 0
net.ipv6.conf.lo.disable_ipv6 = 0
kernel.printk = 5
vm.max_map_count = 262144

and then restart the statefulSet,mongosh, still show the warns：
The server generated these startup warnings when booting
2025-03-18T17:00:03.971+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
2025-03-18T17:00:03.971+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
2025-03-18T17:00:03.971+00:00: We suggest setting the contents of sysfsFile to 0.
2025-03-18T17:00:03.971+00:00: vm.max_map_count is too low

[javsalgar]

This is strange, could you enter the container and run

sysctl -a

[wilburfs]

@javsalgar yes, enter the pod, sysctl -a ：

debug.exception-trace = 1
debug.kprobes-optimization = 1
dev.cdrom.autoclose = 1
dev.cdrom.autoeject = 0
.....
dev.cdrom.info = Can play audio: 1
vm.max_map_count = 262144

but the warn still shown:

The server generated these startup warnings when booting
2025-03-18T17:00:03.971+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
2025-03-18T17:00:03.971+00:00: For customers running the current memory allocator, we suggest changing the contents of the following sysfsFile
2025-03-18T17:00:03.971+00:00: We suggest setting the contents of sysfsFile to 0.
2025-03-18T17:00:03.971+00:00: vm.max_map_count is too low

[javsalgar]

Hi,

If the value is set (as you showed using the output of sysctl -a), then I'd say it's a problem with how mongosh is detecting the resources, not with the Bitnami packaging of MongoDB. My advice would be to report it to the mongodb devs so they can check what's missing.

[wilburfs]

@javsalgar Thank you , I will do as your suggession as update to you.