[
https://issues.apache.org/jira/browse/MESOS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443744#comment-13443744
]
Jie Yu commented on MESOS-262:
------------------------------
I think the challenge here is that how to distinguish between processes that
belong to the executor itself and the processes that belong to the tasks (that
requires the executor to expose some interfaces to the slave). If we can do
this, we can easily create a sub-cgroup in each executor cgroup, and only set
the limit for the sub-cgroup.
> 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
