[
https://issues.apache.org/jira/browse/MESOS-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-2408:
--------------------------
Description: This is tricky in the case when a persistence id is re-used.
When a persistent volume is destroyed explicitly by the framework, master
deletes all information about this volume. That mean the master no longer has
the ability to check if the persistence id is re-used (and reject the later
attempt). On the slave side, we'll use some GC policy to remove directories
associated with deleted persistent volumes (similar to how we GC sandboxes).
That means the persistent volume directory won't be deleted immediately when
the volume is destroyed by the framework explicitly. When the same persistence
id is reused, we'll see the persistent volume still exists and we need to
cancel the GC of that directory (similar to what we cancel the GC for meta
directories during runTask). (was: This is tricky in the case when a
persistence id is re-used. When a persistent volume is destroyed explicitly by
the framework, master deletes all information about this volume. That mean the
master no longer has the ability to check if the persistence id is re-used (and
reject the later attempt). On the slave side, we'll use some GC policy to
remove directories associated with deleted persistent volumes (similar to how
we GC sandboxes). That means the persistent volume directory won't be deleted
immediately when the volume is destroyed by the framework explicitly. When the
same persistence id is reused, we'll see the persistent volume still exists and
we either need to cancel the GC of that directory (similar to what we cancel
the GC for )
> Slave should garbage collect released persistent volumes.
> ---------------------------------------------------------
>
> Key: MESOS-2408
> URL: https://issues.apache.org/jira/browse/MESOS-2408
> Project: Mesos
> Issue Type: Task
> Reporter: Jie Yu
> Assignee: Jie Yu
>
> This is tricky in the case when a persistence id is re-used. When a
> persistent volume is destroyed explicitly by the framework, master deletes
> all information about this volume. That mean the master no longer has the
> ability to check if the persistence id is re-used (and reject the later
> attempt). On the slave side, we'll use some GC policy to remove directories
> associated with deleted persistent volumes (similar to how we GC sandboxes).
> That means the persistent volume directory won't be deleted immediately when
> the volume is destroyed by the framework explicitly. When the same
> persistence id is reused, we'll see the persistent volume still exists and we
> need to cancel the GC of that directory (similar to what we cancel the GC for
> meta directories during runTask).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
