mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8651) Potential memory leaks in the `volume/sandbox_path` isolator
Date Fri, 09 Mar 2018 02:13:00 GMT

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

Jason Lai commented on MESOS-8651:
----------------------------------

Patching for this bug should be fairly easy. [~jieyu], [~gilbert], i think we can release
this fairly quickly once we have patch(es) ready?

> Potential memory leaks in the `volume/sandbox_path` isolator
> ------------------------------------------------------------
>
>                 Key: MESOS-8651
>                 URL: https://issues.apache.org/jira/browse/MESOS-8651
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Jason Lai
>            Assignee: Jason Lai
>            Priority: Major
>              Labels: easyfix, patch
>
> The {{sandboxes}} hashmap object of {{mesos::internal::slave::VolumeSandboxPathIsolatorProcess}}
bears the risk of potential memory leak.
> It [adds the sandbox path upon each container launch|https://github.com/apache/mesos/blob/1.5.x/src/slave/containerizer/mesos/isolators/volume/sandbox_path.cpp#L119-L122]
and does not remove the sandbox path after cleaning up the container. As the life cycle of
an isolator is attached to that of {{MesosContainerizer}}, this means that more and more sandbox
paths will get added to the {{sandboxes}} hashmap object, as Mesos containers keep being launched
and will likely blow up Mesos agent eventually.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message