[MESOS-8279] Persistent volumes are not visible in Mesos UI using default executor on Linux.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2, 1.3.1, 1.4.1
• Fix Version/s: 1.5.0
• Sprint: Mesosphere Sprint 72
• Story Points: 3
• Assignee: Qian Zhang
• Reporter: Jie Yu
• Shepherd: Vinod Kone
• Created: 29/Nov/17 23:23
• Updated: 13/Feb/18 07:24
• Resolved: 17/Jan/18 03:02

Description

The reason is because on Linux, if multiple containers in a default executor want to share a persistent volume, it'll use SANDBOX_PATH volume source with type PARENT. This will be translated into a bind mount in the nested container's mount namespace, thus not visible in the host mount namespace. Mesos UI operates in the host mount namespace.

One potential solution for that is to create a symlink (instead of just a mkdir) in the sandbox. The symlink will be shadowed by the bind mount in the nested container, but in the host mount namespace, it'll points to the corresponding persistent volume.

Issue Links

• causes: MESOS-8460 `Slave::detachFile` can segfault because it could use invalid Framework*.
• depends upon: MESOS-8444 GC failure causes agent miss to detach virtual paths for the executor's sandbox
• relates to: MESOS-8565 Persistent volumes are not visible in Mesos UI when launching a pod using default executor.