incubator-mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <>
Subject [jira] [Assigned] (MESOS-305) Inform the framework about a master failover
Date Tue, 26 Mar 2013 22:41:17 GMT


Benjamin Mahler reassigned MESOS-305:

    Assignee: Benjamin Mahler  (was: Benjamin Hindman)
> Inform the framework about a master failover
> --------------------------------------------
>                 Key: MESOS-305
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>            Assignee: Benjamin Mahler
>            Priority: Critical
> 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
> 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:

View raw message