Skip to content
Documentation

This is the Experimental version (Latest). It is under active development and may change. For the most reliable documentation, use the version selector in the top-right to switch to Stable, or click here to go to the Stable version's homepage.

Perform OS-Level Kernel Tuning

Last updated:

Sysctl: vm.max_map_count

Section titled “Sysctl: vm.max_map_count”

Some components in the Opstella stack (e.g., SonarQube, Elasticsearch-based services) require a higher limit on the number of memory map areas a process may have.

This is REQUIRED for ALL Worker Nodes in your Kubernetes Cluster.

Failure to set this parameter may cause these services to fail to start or crash unexpectedly.

1. Pre-check current value

Run the following command to check the current value on each worker node:

Terminal window
sudo sysctl vm.max_map_count

If the value is greater than or equal to 262144, you can skip this section.

2. Set value permanently

To set this value permanently, add or update the vm.max_map_count setting in /etc/sysctl.conf.

... (deducted)
vm.max_map_count=262144

3. Reload sysctl configuration

Terminal window
sudo sysctl --system
sudo systemctl restart systemd-sysctl

4. Verify the setting

Terminal window
sudo sysctl vm.max_map_count

The output should return 262144.

Finished?

Use the below navigation to proceed