[
https://issues.apache.org/jira/browse/MESOS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman updated MESOS-84:
----------------------------------
Description:
A noticeable memory leak affecting master machines (which host scheduler and
master) has been detected. On one machine, the master was observed consuming a
large amount of memory:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
37908 root 20 0 14.3g 13g 5788 S 2.7 59.3 426:24.17 mesos-master
This appears to affect the scheduler as well, since one machine shows a large
reclaiming of memory coincident with a scheduler process restart.
was:
A noticeable memory leak affecting master machines (which host scheduler and
master) has been detected. On one machine, the master was observed consuming a
large amount of memory:
{code}
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
37908 root 20 0 14.3g 13g 5788 S 2.7 59.3 426:24.17 mesos-master
{code}
This appears to affect the scheduler as well, since one machine shows a large
reclaiming of memory coincident with a scheduler process restart.
> Memory leak in master and scheduler (by way of libmesos.so)
> -----------------------------------------------------------
>
> Key: MESOS-84
> URL: https://issues.apache.org/jira/browse/MESOS-84
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Hindman
>
> A noticeable memory leak affecting master machines (which host scheduler and
> master) has been detected. On one machine, the master was observed consuming
> a large amount of memory:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>
>
>
> 37908 root 20 0 14.3g 13g 5788 S 2.7 59.3 426:24.17 mesos-master
> This appears to affect the scheduler as well, since one machine shows a large
> reclaiming of memory coincident with a scheduler process restart.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira