[
https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972310#comment-13972310
]
Bernd Mathiske commented on MESOS-336:
--------------------------------------
Good to know that the base name, not the whole URI, defines the identity of a
resource. We can build something simple like that and it will still be useful.
There will just have to be extra rules for frameworks/users that do not have to
be followed when using the current download-always mode.
Example rule: when using caching resource base names must be uniquely named
within the same framework. We do not demand that they be unique across
frameworks, though (I hope). So I suggest we make a separate cache per active
framework. Otherwise there could be thrashing from multiple like-named
resources from different frameworks.
Thanks for also explaining how the framework gets hold of the checksum! By
placing the resource at the URL itself! I was under the (false?) impression
that this was not generally the 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)
