Last time I tried (not on the latest release) I also had to have cgroups set to limit swap, otherwise as soon as the process hit the RAM limit it would just start to consume swap.
try adding --cgroups_limit_swap to the slaves startup flags. On 17 March 2016 at 16:21, Shiyao Ma <[email protected]> wrote: > Hi, > > > For the slave side: > export MESOS_RESOURCES='cpus:4;mem:180' > export MESOS_ISOLATION='cgroups/cpu,cgroups/mem' > > For the framework, > It accepts the offer from the slave and sends tasks with memory spec less > than offered. > > > However, the task actually *deliberately* asks for an arbitrary large memory > during runtime. > > My assumption is that the slave will kill the task. However, it doesn't. > > So here goes my question. How does slave handle the 'runtime memory > exceeding cgroup limit' behavior? Will any handlers be invoked? > > > > Regards.
