You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2014/11/11 18:02:33 UTC

[jira] [Comment Edited] (MESOS-336) Mesos slave should cache executors

    [ https://issues.apache.org/jira/browse/MESOS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206623#comment-14206623 ] 

Bernd Mathiske edited comment on MESOS-336 at 11/11/14 5:01 PM:
----------------------------------------------------------------

It is now an epic and there are subtickets that can as far as I estimate be implemented within a sprint or less each, given the available prior work from the first attempt at MESOS-336.


was (Author: bernd-mesos):
It is now an epic and there are subtickets that can as far as I estimate be implemented within a sprint each, given the available prior work from the first attempt at MESOS-336.

> Mesos slave should cache executors
> ----------------------------------
>
>                 Key: MESOS-336
>                 URL: https://issues.apache.org/jira/browse/MESOS-336
>             Project: Mesos
>          Issue Type: Epic
>          Components: slave
>            Reporter: brian wickman
>            Assignee: Bernd Mathiske
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> 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.3.4#6332)