Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 21 Jul 2016 18:17:20 +0000 (UTC)
From: "Avinash Sridharan (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12991525.1469118752000.98266.1469125040493@Atlassian.JIRA>
In-Reply-To: <JIRA.12991525.1469118752000@Atlassian.JIRA>
References: <JIRA.12991525.1469118752000@Atlassian.JIRA> <JIRA.12991525.1469118752376@arcas>
Subject: [jira] [Assigned] (MESOS-5879) cgroups/net_cls isolator causing
 agent recovery issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 21 Jul 2016 18:17:22 -0000


     [ https://issues.apache.org/jira/browse/MESOS-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Avinash Sridharan reassigned MESOS-5879:
----------------------------------------

    Assignee: Avinash Sridharan

> cgroups/net_cls isolator causing agent recovery issues
> ------------------------------------------------------
>
>                 Key: MESOS-5879
>                 URL: https://issues.apache.org/jira/browse/MESOS-5879
>             Project: Mesos
>          Issue Type: Bug
>          Components: cgroups, isolation, slave
>            Reporter: Silas Snider
>            Assignee: Avinash Sridharan
>
> We run with 'cgroups/net_cls' in our isolator list, and when we restart any agent process in a cluster running an experimental custom isolator as well, the agents are unable to recover from checkpoint, because net_cls reports that unknown orphan containers have duplicate net_cls handles.
> While this is a problem that needs to be solved (probably by fixing our custom isolator), it's also a problem that the net_cls isolator fails recovery just for duplicate handles in cgroups that it is literally about to unconditionally destroy during recovery. Can this be fixed?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)