[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198690#comment-14198690
]
Bernd Mathiske commented on MESOS-336:
--------------------------------------
Here is what happened. Other things had higher priority and so this patch never
got full review attention. Meanwhile, pressure to create smaller patches also
increased, which further reduced the priority of this one.
MESOS-1316 and MESOS-1248 were held back, waiting for MESOS-336. All three
stalled, a lot has happened and MESOS-336 is yet again harder to rebase. So a
change in strategy was proposed by Ben: land MESOS-1316 first, then MESOS-1248,
then MESOS-336. I have now created and proposed patches for the former 2 and am
starting to rebase, really re-implement, MESOS-336.
In doing so, I want to create much smaller patches. Furthermore I have devised
a concurrency-safe cache eviction scheme that respects space quota. This will
add more patches. Hence, it is now time to convert MESOS-336 to an epic and
create subordinate tickets.
> Mesos slave should cache executors
> ----------------------------------
>
> Key: MESOS-336
> URL: https://issues.apache.org/jira/browse/MESOS-336
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: brian wickman
> Assignee: Bernd Mathiske
> Labels: newbie
>
> The slave should be smarter about how it handles pulling down executors. In
> our environment, executors rarely change but the slave will always pull it
> down from regardless HDFS. This puts undue stress on our HDFS clusters, and
> is not resilient to reduced HDFS availability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
