Gilbert Song commented on MESOS-8565:

Please note that this fix addresses the issue that persistent volume is shared 
to nested containers by defining a `SANDBOX_PATH` volume to each nested 
container from the framework. So that the persistent volume would show up on 
the Mesos UI.

However, there is a related *limitation*: for the case of only `SANDBOX_PATH` 
volume being specified for a nested container (no persistent volume or any 
other volume is specified at the executor container level), the pure 
`SANDBOX_PATH` volume is not reflected on the UI yet. We should create a 
separate Jira for this case. /cc [~qianzhang]

> Persistent volumes are not visible in Mesos UI when launching a pod using 
> default executor.
> -------------------------------------------------------------------------------------------
>                 Key: MESOS-8565
>                 URL: https://issues.apache.org/jira/browse/MESOS-8565
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.2.2, 1.3.1, 1.4.1
>            Reporter: Qian Zhang
>            Assignee: Qian Zhang
>            Priority: Major
>             Fix For: 1.6.0, 1.5.1
> When user launches a pod to use a persistent volume in DC/OS, the nested 
> containers in the pod can access the PV successfully and the PV directory of 
> the executor shown in Mesos UI has all the contents written by the tasks, but 
> the PV directory of the tasks shown in DC/OS UI and Mesos UI is empty.

This message was sent by Atlassian JIRA

Reply via email to