You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "jhiuvg (JIRA)" <ji...@apache.org> on 2016/05/12 20:21:12 UTC

[jira] [Updated] (MESOS-4259) mesos HA can't delete the the redundant container on failure slave node.

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

jhiuvg updated MESOS-4259:
--------------------------
    Attachment: canon.pdf

> mesos HA can't delete the  the redundant container on failure slave node.
> -------------------------------------------------------------------------
>
>                 Key: MESOS-4259
>                 URL: https://issues.apache.org/jira/browse/MESOS-4259
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker, framework
>    Affects Versions: 0.25.0
>            Reporter: wangqun
>            Priority: Critical
>              Labels: patch
>             Fix For: 0.25.0
>
>         Attachments: canon.pdf
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> We have setup one mesos cluster. One Master nodes, and two slave nodes.
> We want to test the HA, but we find the mesos HA can't delete the  the redundant container on failure slave node.
> 1.We create one container on slave node. 
> 2.stop the slave node having the container,and the container can transfer to the remaining slave node. 
> However, if we restore the slave node stoped by us. The status of the original container is exited. Then I start the container manually and it can start up. i.e. There are two contain is running on different slave node.
> I think that the container and new container is repeated after migration. They are redundant. Can mesos delete automatically the redundant container?



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