You can add a large negative score to the /proc/[ovs-vswitchd-PID]/oom_score_adj file to ensure that your process gets a lower chance of being picked and terminated by OOM killer e.g "echo -500 > /proc/[ovs-vswitchd-PID]/oom_score_adj". The oom_score_adj can vary from -1000 to 1000. If you assign -1000 to it, it can use 100% memory and still avoid getting terminated by OOM killer. Be aware that this change valid until reboot or service restart. If you want that the value in oom_score_adj persists after a reboot or service restart than add "oom score -500" to the /etc/init/openvswitch-switch.conf file and restart the openvswitch-switch service.
Hi Alexander,
You can add a large negative score to the /proc/[ ovs-vswitchd- PID]/oom_ score_adj file to ensure that your process gets a lower chance of being picked and terminated by OOM killer e.g "echo -500 > /proc/[ ovs-vswitchd- PID]/oom_ score_adj" . The oom_score_adj can vary from -1000 to 1000. If you assign -1000 to it, it can use 100% memory and still avoid getting terminated by OOM killer. Be aware that this change valid until reboot or service restart. If you want that the value in oom_score_adj persists after a reboot or service restart than add "oom score -500" to the /etc/init/ openvswitch- switch. conf file and restart the openvswitch-switch service.