[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974258#comment-13974258
]
Bernd Mathiske commented on MESOS-336:
--------------------------------------
I understand that there is elegance in leaving all aspects of fetching
contained in the external fetcher program. Nice separation of concern. But we
can have that cake and eat it, too!
A flag "if asking for caching, let the fetcher program handle it" can indicate
that caching should be dealt with externally. I just would not like to write
that external cache quite yet, because it does less with more code. We can
leave this to third parties. As a first step, I am instead proposing to focus
on a caching scheme dealt with by the MesosContainerizerProcess.
> 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)
