[jira] [Resolved] (MESOS-940) Slave should checkpoint bootid after recovery instead of after registration

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

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

Vinod Kone resolved MESOS-940.
------------------------------

    Resolution: Fixed

commit d259083342d205a266322017139fdd66807be41c
Author: Vinod Kone <vi...@twitter.com>
Date:   Thu Jan 23 10:09:31 2014 -0800

    Fixed slave to checkpoint boot id immediately after recovery.
    
    Review: https://reviews.apache.org/r/17229/


> Slave should checkpoint bootid after recovery instead of after registration
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-940
>                 URL: https://issues.apache.org/jira/browse/MESOS-940
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.16.0
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>             Fix For: 0.16.0
>
>
> Doing it after registration means that the slave could keep failing to recover in certain scenarios.
> Example scenario:
> --> A pre 0.16.0 slave was upgraded to 0.16.0
> --> After a slave roll it *re-registered* with the master and hence never wrote the boot id
> --> Now if machine reboots and slave info is incompatible the slave fails immediately during recovery.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)