[MESOS-2408] Slave should reclaim storage for destroyed persistent volumes.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: agent
• Labels: mesosphere persistent-volumes
• Epic Link: Persistence
• Sprint: Twitter Mesos Q3 Sprint 1, Mesosphere Sprint 31
• Story Points: 5
• Assignee: Neil Conway
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 26/Feb/15 00:53
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

Description

At present, destroying a persistent volume does not cleanup any filesystem space that was used by the volume (it just removes the Mesos-level metadata about the volume). This effectively leads to a storage leak, which is bad. For task sandboxes, we do "garbage collection" to remove the sandbox at a later time to facilitate debugging failed tasks; for volumes, because they are explicitly deleted and are not tied to the lifecycle of a task, removing the associated storage immediately seems best.

To implement this safely, we'll either need to ensure that libprocess messages are delivered in-order, or else add some extra safe-guards to ensure that out-of-order CheckpointResources messages don't lead to accidental data loss.

Issue Links

• relates to: MESOS-9352 Data in persistent volume deleted accidentally when using Docker container and Persistent volume