You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2016/12/27 02:29:58 UTC
[jira] [Updated] (MESOS-6264) Investigate the high memory usage of
the default executor.
[ https://issues.apache.org/jira/browse/MESOS-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-6264:
--------------------------
Component/s: executor
> Investigate the high memory usage of the default executor.
> ----------------------------------------------------------
>
> Key: MESOS-6264
> URL: https://issues.apache.org/jira/browse/MESOS-6264
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Reporter: Anand Mazumdar
> Labels: mesosphere
> Attachments: pmap_output_for_the_default_executor.txt
>
>
> It seems that a default executor with two sleep tasks is using ~32 mb on average and can sometimes lead to it being killed for some tests like {{SlaveRecoveryTest/0.ROOT_CGROUPS_ReconnectDefaultExecutor}} on our internal CI. Attached the {{pmap}} output for the default executor. Please note that the command executor memory usage is also pretty high (~26 mb).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)