Thanks - that makes sense. Have stopped running with the --cgroups_limit_swap option and confirm the limit_in_bytes is now set.
Not ideal as we'll start eating swap now - but hopefully should be able to get an upgrade before that becomes a real problem. On 28 April 2015 at 18:59, Ian Downes <idow...@twitter.com> wrote: > Ahh, my bad I should have looked more closely at your version. This was a > bug that was introduced when the memsw functionality came in and then fixed > in 0.22.0. > > See: > https://issues.apache.org/jira/browse/MESOS-2128 > commit 24cb10a2d68 > > I suggest upgrading to >= 0.22.0 or, if that's not desirable, do not use the > cgroups_limit_swap flag. > > Ian > > On Tue, Apr 28, 2015 at 10:45 AM, Dick Davies <d...@hellooperator.net> > wrote: >> >> You may very well be right, but I'd like to keep this specific thread >> focussed on figuring >> out why the expected/implemented behaviour isn't happening in my case >> if that's ok. >> >> On 28 April 2015 at 19:26, CCAAT <cc...@tampabay.rr.com> wrote: >> >> > I really hate to be the 'old fashion computer scientist' in this group, >> > but, I think that the role of and usage of 'cgroups' is going to have to >> > be expanded greatly as a solution to the dynamic memory management needs >> > of >> > both the cluster(s) and the frameworks. This problem is not going away >> > and I >> > see no other serious solution to cgroup use expansion. > >
