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 <[email protected]> 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 <[email protected]> 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. >
