You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2012/08/29 03:47:07 UTC

[jira] [Commented] (MESOS-262) Slave should not charge the resources required for launching a executor against the executor

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

Jie Yu commented on MESOS-262:
------------------------------

>From the title, are you suggesting that we should not set a resource limit for the executor itself, but only limit the resource usage by all tasks in an executor?
                
> Slave should not charge the resources required for launching a executor against the executor 
> ---------------------------------------------------------------------------------------------
>
>                 Key: MESOS-262
>                 URL: https://issues.apache.org/jira/browse/MESOS-262
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>
> This is exacerbated when using cgroups isolation module on the slave.
> At Twitter, we have seen this manifest as executors being killed by the cgroups isolation module. This happened because the high memory footprint of the hdfs download (~400MB) of the executor exceeds the memory requested by the executor (128MB) for itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira