mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <>
Subject [jira] [Updated] (MESOS-2408) Slave should reclaim storage for destroyed persistent volumes.
Date Thu, 10 Mar 2016 23:10:40 GMT


Neil Conway updated MESOS-2408:
    Component/s: slave

> Slave should reclaim storage for destroyed persistent volumes.
> --------------------------------------------------------------
>                 Key: MESOS-2408
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>          Components: slave
>            Reporter: Jie Yu
>            Assignee: Neil Conway
>              Labels: mesosphere, persistent-volumes
> 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.

This message was sent by Atlassian JIRA

View raw message