mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7225) Tasks launched via the default executor cannot access disk resource volumes.
Date Thu, 16 Mar 2017 16:08:41 GMT

     [ https://issues.apache.org/jira/browse/MESOS-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anand Mazumdar updated MESOS-7225:
----------------------------------
    Labels: mesosphere  (was: )

> Tasks launched via the default executor cannot access disk resource volumes.
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-7225
>                 URL: https://issues.apache.org/jira/browse/MESOS-7225
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Anand Mazumdar
>            Assignee: Anand Mazumdar
>              Labels: mesosphere
>
> Currently, when a task in a task group tries to access a volume specified in disk resources
(e.g., persistent volumes), it doesn't have access to them since they are mounted in the root
container (executor). This happens due to there being no mechanism to specify resources for
child containers yet. Hence, by default any resources (e.g., disk) are added to the root container.
> A possible solution can be to set up the mapping manually by the default executor using
the {{SANDBOX_PATH}} volume source type giving child containers access to the volume mounted
in the parent container. This is at best a workaround and the ideal solution would be tackled
as part of MESOS-7207.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message