[MESOS-2523] Executor directory has incorrect permissions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Michael Ngo
• Created: 20/Mar/15 01:46
• Updated: 06/Apr/15 22:38
• Resolved: 06/Apr/15 22:38

Description

Currently my setup involves a mesos master on one node (nodeMM) and a mesos slave on another node (nodeMS). NodeMM runs the mesos-master process as the "flxjob" user. The framework (Chronos) attached to nodeMM submits tasks as the "flxjob" user. NodeMS runs the mesos-slave process as "root" cause cgroups are being used.

What's expected to happen is that the executed task will be executed by "flxjob" and that directory in which code is executed is also owned by "flxjob". What actually happens is that the task is executed by "flxjob," but the directory in which code is executed is owned by "root."

Here are the arguments used by each process.

• Master

  /usr/local/sbin/mesos-master --cluster=Mesos HA Cluster --log_dir=/var/log/mesos/master --work_dir=/var/lib/mesos/master --zk=zk://172.16.3.70:2181/mesos --hostname=ip-172-16-15-74 --quorum=1 --zk_session_timeout=10secs --no-root_submissions

• Slave

  /usr/local/sbin/mesos-slave --log_dir=/var/log/mesos/slave --work_dir=/var/lib/mesos/slave --master=zk://172.16.3.70:2181/mesos --hostname=172.16.3.215 --ip=172.16.3.215 --cgroups_enable_cfs --cgroups_hierarchy=/cgroup --isolation=cgroups/cpu,cgroups/mem --cgroups_limit_swap

Here is the output for returning the user identity via the "id" process. Both the working (expected) and not working scenario yield the same output.

uid=501(flxjob) gid=501(flxjob) groups=501(flxjob),0(root)

I narrowed down where the issue was introduced. It was introduced by this commit.

Issue Links

• is duplicated by: MESOS-2592 The sandbox directory is not chown'ed if the fetcher doesn't run