[
https://issues.apache.org/jira/browse/MESOS-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-2070:
-----------------------------------
Sprint: Mesosphere Q1 Sprint 1 - 1/23, Mesosphere Q1 Sprint 2 - 2/6,
Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1
Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17,
Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15, Mesosphere Sprint
10, Mesosphere Sprint 11 (was: Mesosphere Q1 Sprint 1 - 1/23, Mesosphere Q1
Sprint 2 - 2/6, Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6,
Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1
Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15,
Mesosphere Sprint 10)
> Implement simple slave recovery behavior for fetcher cache
> ----------------------------------------------------------
>
> Key: MESOS-2070
> URL: https://issues.apache.org/jira/browse/MESOS-2070
> Project: Mesos
> Issue Type: Improvement
> Components: fetcher, slave
> Reporter: Bernd Mathiske
> Assignee: Bernd Mathiske
> Labels: newbie
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> Clean the fetcher cache completely upon slave restart/recovery. This
> implements correct, albeit not ideal behavior. More efficient schemes that
> restore knowledge about cached files or even resume downloads can be added
> later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
