[jira] [Assigned] (MESOS-305) Inform the framework about a master failover

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

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

Vinod Kone reassigned MESOS-305:
--------------------------------

    Assignee: Benjamin Hindman

This seems to be causing a slew of LOST tasks @Twitter, whenever a master failsover.

[~benjaminhindman] would you have some time to take a look at this and see if we there is a short-term fix for this. IIUC, we were waiting on leader detector refactor before fixing this.
                
> Inform the framework about a master failover
> --------------------------------------------
>
>                 Key: MESOS-305
>                 URL: https://issues.apache.org/jira/browse/MESOS-305
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>            Assignee: Benjamin Hindman
>
> With the recent changes in the master detecter code, we no longer send 'NoMasterDetected' to the scheduler driver, which in turn means the 'disconnected' scheduler callback is never invoked.
> At Twitter this manifested as a spew of LOST tasks whenever a master failover happens. This is because the scheduler holds on to offers for a while and never knows about the invalidity of offers, until after tasks are launched. Though this is a race, it is ideal to minimize this window as much as possible by informing the scheduler of the master failover.

--
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