It turns out everything works if you set permissions appropriately of
$CGROUP_ROOT/mesos/$TASKID/ so the yarn user can write to the hierarchy.
Then all works exactly as expected.
I spent a while running through the container-executor code and when it
mounts a cgroup subsystem it changes the
Santosh, that is the behavior I'm seeing.
On May 4, 2016 6:13 PM, "Santosh Marella" wrote:
> > The second involves the cgroup hierarchy and the cgroup mount point.
> Here
> > the code attempts to create a hierarchy in $CGROUP_DIR/mesos/$TASK_ID.
> > This is problematic as
> The second involves the cgroup hierarchy and the cgroup mount point. Here
> the code attempts to create a hierarchy in $CGROUP_DIR/mesos/$TASK_ID.
> This is problematic as mesos will not unmount the hierarchy when the task
> finished (in this case the node manager)
IIRC, when a task is
I've been digging into groups support, there's a few things that are easy
fixes but a few things become problematic so I'd like to discuss.
First the code makes certain options dictated that can be placed in the
yarn-site.xml - this should be done to remove code and provide
flexibility. That's