[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970157#comment-13970157
]
Vinod Kone commented on MESOS-336:
----------------------------------
But it is safe to re-download right? Anyway, I agree that using time is not a
good idea in general. There are other issues like clock synchronization etc.
This is what I propose:
--> First optimize for network downloads
Introduce md5/hash in CommandInfo as suggested in MESOS-700.
--> In a subsequent review lets see if we can cleanly optimize for local copies
Maybe symlinks are the solution here. Or maybe using some kind of
read-write container images with low filesystem setup cost (ala docker).
> 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)
