You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Silas Snider (JIRA)" <ji...@apache.org> on 2016/08/04 20:47:20 UTC
[jira] [Commented] (MESOS-5879) cgroups/net_cls isolator causing
agent recovery issues
[ https://issues.apache.org/jira/browse/MESOS-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408452#comment-15408452 ]
Silas Snider commented on MESOS-5879:
-------------------------------------
Have you made much progress on this? I'm asking because I got permission to contribute back the fix we're using right now, which just ignores child cgroups in the net_cls isolator.
> 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
> Labels: mesosphere
>
> 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)