[jira] [Updated] (MESOS-614) Master should remove checkpointing slave that gets disconnected when the new slave tries to register

["Vinod Kone (JIRA)" <ji...@apache.org>]

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

Vinod Kone updated MESOS-614:
-----------------------------

    Issue Type: Bug  (was: Improvement)
    
> Master should remove checkpointing slave that gets disconnected when the new slave tries to register
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-614
>                 URL: https://issues.apache.org/jira/browse/MESOS-614
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>             Fix For: 0.13.0
>
>
> When a checkpointing slave is not able to recover (for whatever reason) it tries to register as a new slave. But if this registration happens before master has removed the old slave, the master simply gives the old slave id for the new slave. This means the master thinks the slave is running a bunch of tasks whereas the slave thinks it is new.
> Master should remove the slave from its map (send TASK_LOST updates) when this happens and create a new slave entry.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira