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

Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/09/28 03:38:20 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 ]

Anand Mazumdar updated MESOS-6264:
----------------------------------
    Attachment: pmap_output_for_the_default_executor.txt

> 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
>            Reporter: Anand Mazumdar
>              Labels: mesosphere
>             Fix For: 1.0.0
>
>         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)