You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2015/03/26 23:57:53 UTC
[jira] [Assigned] (MESOS-2547) Cleanup stale bind mounts for port
mapping isolator during slave recovery.
[ https://issues.apache.org/jira/browse/MESOS-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jie Yu reassigned MESOS-2547:
-----------------------------
Assignee: Jie Yu
> Cleanup stale bind mounts for port mapping isolator during slave recovery.
> --------------------------------------------------------------------------
>
> Key: MESOS-2547
> URL: https://issues.apache.org/jira/browse/MESOS-2547
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 0.21.0, 0.21.1, 0.22.0
> Reporter: Jie Yu
> Assignee: Jie Yu
>
> Leaked bind mount under /var/run/netns for port mapping isolator is a known issue. There are many ways it can get leaked. For example, if the slave crashes after creating the bind mount but before creating the veth, the bind mount will be leaked. Also, if the detached unmount does not finish in time and the subsequent os::rm fails, the bind mount will be leaked as well.
> Since leaked bind mount is inevitable, we need to clean them up during startup (slave recovery).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)