[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972947#comment-13972947
]
Bernd Mathiske commented on MESOS-336:
--------------------------------------
I think I have all I need for a minimal first patch now. Thanks a lot to you
all for filling me in on what your objectives are for this ticket. We are
focusing on what seems to be the most common case: a highly cooperative
framework with all URIs firmly in framework possession. Then it should be
possible to implement a first tack with a few fetcher program upgrades and
minor slave/containerizer changes (fetchDir flag, md5 URI field).
> 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.2#6252)
