[
https://issues.apache.org/jira/browse/MESOS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605022#comment-14605022
]
Jie Yu commented on MESOS-2603:
-------------------------------
{quote}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.{quote}
I think there's an even bigger issue that needs to be resolved first.
Currently, all resources in mesos are exclusive, meaning that if a resource is
used by one task/executor, it cannot be concurrently used by other
executor/task. We don't currently have a notion of "shared resources".
{quote}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).{quote}
Totally, [[email protected]], can you add a TODO about that in your latest
patch?
> 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)
