You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 20:16:54 UTC
[jira] [Created] (MESOS-84) Memory leak in master and scheduler (by
way of libmesos.so)
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:
{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.
--
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
[jira] [Resolved] (MESOS-84) Memory leak in master and scheduler
(by way of libmesos.so)
Posted by "Benjamin Hindman (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Hindman resolved MESOS-84.
-----------------------------------
Resolution: Fixed
Assignee: Charles Reiss
Charles used valgrind to route out memory leaks. There still might be some leaks in the JNI bindings, but since we experienced this for the master (which doesn't use the JNI bindings) I'm closing it for now. We can always re-open or create a new one if we run across the memory leak issues again.
> 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
> Assignee: Charles Reiss
>
> 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
[jira] [Updated] (MESOS-84) Memory leak in master and scheduler (by
way of libmesos.so)
Posted by "Benjamin Hindman (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (MESOS-84) Memory leak in master and scheduler
(by way of libmesos.so)
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205775#comment-13205775 ]
jiraposter@reviews.apache.org commented on MESOS-84:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3783/
-----------------------------------------------------------
(Updated 2012-02-10 21:27:41.014694)
Review request for mesos and Benjamin Hindman.
Summary
-------
This fixes some memory leaks of utility classes found through valgrind:
- the Slave never frees its Framework or Executor objects (this probably only affects the tests);
- the Master does not free its TaskDescriptionVisitor objects properly because the superclass does not have a virtual destructor (this is likely a slow memory leak for a running Master);
This addresses bug MESOS-84.
https://issues.apache.org/jira/browse/MESOS-84
Diffs
-----
src/master/master.cpp fd9e6fd
src/slave/slave.cpp 9b33a5a
Diff: https://reviews.apache.org/r/3783/diff
Testing
-------
Thanks,
Charles
> 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