Linux OOM recommended settings for Bitbucket
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
Linux OutOfMemory system configuration recommendations. Linux OOM killer should be on and configured in the following way.
Bitbucket Data Center running on Linux.
Run these commands to see the current configuration of Linux OutOfMemory killer:
cat /proc/sys/vm/oom_kill_allocating_task cat /proc/sys/vm/overcommit_memory cat /proc/sys/vm/panic_on_oom
- oom_kill_allocating_task: This enables or disables killing the OOM-triggering task in out-of-memory situations.
- 0: "OOM killer will scan through the entire tasklist and select a task based on heuristics to kill";
- If this is set to non-zero, the OOM killer simply kills the task that triggered the out-of-memory condition. If oom_kill_allocating_task is set to 1 and the system runs out of memory, the process killed will not be Bitbucket.
- panic_on_oom is a trinary value:
- 0 = "the kernel will kill some rogue process";
- 1 and 2 = "the kernel panics when out-of-memory happens."
- overcommit_memory is a trinary value:
- 0 = "Estimate if enough memory";
- 1 = "Always say Yes";
- 2 = "Say no if out of memory to the process". If overcommit_memory is set to 0 or 1 and the system runs out of memory, the process, most commonly a git process with Bitbucket, will be killed.
Make sure the system is configured in one of the following ways. To check live, check these values in proc:
/proc/sys/vm/oom_kill_allocating_task = 1 /proc/sys/vm/overcommit_memory = 2 /proc/sys/vm/panic_on_oom = 0
To check from /etc/sysctl.conf file:
vm.oom_kill_allocating_task = 1 vm.overcommit_memory = 2 vm.panic_on_oom = 0