[
https://issues.apache.org/jira/browse/MESOS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605008#comment-14605008
]
Benjamin Hindman commented on MESOS-2603:
-----------------------------------------
There is a deeper systematic issue here that needs to be resolved, we need to
add user information (and possibly also group information) to the persistent
volume that gets created. As [[email protected]] points out, his fix is just
temporary in the event that multiple frameworks running under the same role but
with executors with different usernames attempt to use the same persistent
volume.
Given that this feature is just going down for alpha right now I'm okay with
this "fix" provided we clearly document in the code it's shortcomings and the
proposed plan (i.e., adding user/group to persistent volumes).
> Permissions and ownership of persistent volumes are not set correctly.
> ----------------------------------------------------------------------
>
> Key: MESOS-2603
> URL: https://issues.apache.org/jira/browse/MESOS-2603
> Project: Mesos
> Issue Type: Bug
> Reporter: Jie Yu
> Assignee: haosdent
> Priority: Critical
>
> Right now, we don't change the owner/group of the persistent volume created
> by slave and the default permission is 755. If slave is running under root, a
> non-root task won't be able to create files in the persistent volume.
> One way is to set the owner/group of the persistent volume to be
> frameworkInfo.user. But what if the commandInfo of the executor uses a
> different user?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
