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 2015/08/05 13:22:04 UTC

[jira] [Commented] (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=14655217#comment-14655217 ] 

Bernd Mathiske commented on MESOS-336:
--------------------------------------

By spinning off MESOS-2073 into its own epic, this one can now be regarded as completed. 
(That we are only using two-level hierarchies to break down tickets led to this repositioning.)

> 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
>              Labels: mesosphere
>   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)