This is the Stable version of the documentation. The latest version is experimental and under active development. You can use the version selector in the top-right menu to switch versions for this specific page, or click here to go to the latest version's homepage.
Perform OS-Level Kernel Tuning
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:
sudo sysctl vm.max_map_countIf 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=2621443. Reload sysctl configuration
sudo sysctl --systemsudo systemctl restart systemd-sysctl4. Verify the setting
sudo sysctl vm.max_map_countThe output should return 262144.
Finished?
Use the below navigation to proceed