[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968947#comment-13968947
]
Bernd Mathiske commented on MESOS-336:
--------------------------------------
All that said, the default behavior should be exactly what it is now and all
other variants need to be explicitly asked for with extra flags/arguments. In
total, we are looking at the following flag-switchable alternatives:
- Download each and every time (the default now and then).
- Download only once, the reuse cache.
- Framework asks for a specific checksum, download if not found in cache. Note
that this variant does NOT probe the URI for a checksum as the next variant
does.
- Probe the checksum at the URI each and every time, download every time the
checksum changed.
Another switch indicates whether tasks get separate copies.
This is getting complex. Feedback welcome.
> 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)
