[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972019#comment-13972019
]
Davis Wamola commented on MESOS-336:
------------------------------------
Are you planning on addressing the issue that the current implementation of
fetcher downloads and extract the files in place and then copies them to their
final location which is I/O intensive instead of streaming it to the final
location?
If you cache it and only soft-link as you initially suggested then it wouldn’t
be a problem, but you said symlinks wouldn’t work for the general case.
> 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)
