Comment 4 for bug 1814046

Alexander, setting any OOM-killer value is tightly connected to the real environment's characteristics. Since we find memory leaks as a rare-to-none occurring event we don't see any reason to change anything there. Moreover, neither a Controller node or a Compute nodes have any sacrificial processes that are not important for proper OpenStack operations. You just cannot save everything, since making priorities for every process effectively means that no process has a priority (exactly what we have now). Additionally, a memory leak should be fixed, not worked around or masked, otherwise it may be hiding until it's too late and all the data is lost. OpenStack is designed to have a failover in case if one of the nodes is failed, this idea allows cloud operators to troubleshoot the failed node, learn the lesson and avoid it re-occurrence in the future.