mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7927) The composing containerizer leaks memory in some scenarios.
Date Wed, 13 Sep 2017 07:10:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164233#comment-16164233
] 

Qian Zhang commented on MESOS-7927:
-----------------------------------

commit 257ee17400dcf66f69d526d768c8fdc1b1740004
Author: Qian Zhang zhq527725@gmail.com
Date:   Tue Sep 12 15:17:43 2017 +0800

Fixed a memory leak in composing containerizer.

Review: https://reviews.apache.org/r/62237

src/slave/containerizer/composing.cpp | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

> The composing containerizer leaks memory in some scenarios.
> -----------------------------------------------------------
>
>                 Key: MESOS-7927
>                 URL: https://issues.apache.org/jira/browse/MESOS-7927
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Anand Mazumdar
>            Assignee: Qian Zhang
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> The composing containerizer does not remove an active containers from its internal {{containers}}
hashmap containing the known active containers in some cases. This can happen when the container
terminates on its own. This means that {{destroy()}} is not invoked for such containers.
> Ideally, we should chain the {{destroy}} callback when launching the container itself.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message