[
https://issues.apache.org/jira/browse/MESOS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443754#comment-13443754
]
Jie Yu commented on MESOS-262:
------------------------------
Oh! now I get it! Correct me if I am wrong:
1) slave tries to launch an executor
2) CgroupsIsolationModule::launchExecutor is invoked
3) resource limit is set for the new executor (by invoking the resourcesChanged
function)
4) the child process (after fork) invokes ExecutorLauncher::run()
5) the hdfs download in run() use more memory than requested by the executor
6) the executor get killed by the isolation module
> 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
