Description of problem:
when we set a memory limit for gluster processes through cgroup tunable scripts, as introduced in BZ#1484446, we don't OOM kill the gluster process when the memory limit is hit.
While we don't want to default to OOM kill, however user must be given an option to configure this.
refer the validation comment in https://bugzilla.redhat.com/show_bug.cgi?id=1484446#c9
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.set memory limit through cgroup tunable using gluster script ./control-mem.sh
user must be prompted to know if OOM kill should happen when memory limit is hit
However if we are implementing this, we must make sure we are NOT making it default.
Also, we must through a warning if a user is trying to set this
Not working on this in near term. If QE is OK, we can close it as DEFERRED and work on it later point in time.
(In reply to Amar Tumballi from comment #4)
> Not working on this in near term. If QE is OK, we can close it as DEFERRED
> and work on it later point in time.
I am ok with closing this bug as deferred or won't fix