[
https://issues.apache.org/jira/browse/MESOS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482123#comment-14482123
]
Niklas Quarfot Nielsen commented on MESOS-2592:
-----------------------------------------------
Joris and I have been talking about a few options:
1) Always run the fetcher. The fetcher currently sets the owner on the executor
directory while iterating the URI's, so that would have to be fixed first off.
2) Set the owner when the executor directory is created in
createExecutorDirectory() (I attached a patch which shows how that looks like).
It is a fairly localized change, but the overlap of having the fetcher _and_
the slave setting the owner is not very clean.
3) Have the containerizer set it.
> The sandbox directory is not chown'ed if the fetcher doesn't run
> ----------------------------------------------------------------
>
> Key: MESOS-2592
> URL: https://issues.apache.org/jira/browse/MESOS-2592
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.22.0
> Reporter: Niklas Quarfot Nielsen
> Priority: Blocker
> Attachments: switchUser.patch
>
>
> We have run into issues with the sandbox permissions and ownership. It looks
> like the sandbox isn't chown'ed if no URIs are put in the task info. Recent
> changes have moved the chown'ing from the containerizer to the fetcher,
> however if the fetcher isn't run - the sandbox owner will remain the user of
> the slave (in our case, root).
> Have anyone run into something similar?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
