You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "haosdent (JIRA)" <ji...@apache.org> on 2016/09/05 09:36:20 UTC

[jira] [Updated] (MESOS-6126) Support to enable new isolators after Mesos Agent restart

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

haosdent updated MESOS-6126:
----------------------------
    Description: Now when Mesos Agent restart with new isolation flags, Mesos Agent would {{Isolator::update}} failed on those exist containers. In this case, we should skip to update them if those containers could not {{Isolator::recover}} success before.   (was: Now when Mesos Agent restart with new isolation flags, Mesos Agent would {{Isolator::update}} failed on those exist containers. In this cases, we should skip to update them if those containers could not {{Isolator::recover}} success before. )

> Support to enable new isolators after Mesos Agent restart
> ---------------------------------------------------------
>
>                 Key: MESOS-6126
>                 URL: https://issues.apache.org/jira/browse/MESOS-6126
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: haosdent
>              Labels: isolation, isolator
>
> Now when Mesos Agent restart with new isolation flags, Mesos Agent would {{Isolator::update}} failed on those exist containers. In this case, we should skip to update them if those containers could not {{Isolator::recover}} success before. 



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