Return-Path: X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 64505F81D for ; Wed, 20 Mar 2013 00:43:15 +0000 (UTC) Received: (qmail 48876 invoked by uid 500); 20 Mar 2013 00:43:15 -0000 Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org Received: (qmail 48844 invoked by uid 500); 20 Mar 2013 00:43:15 -0000 Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mesos-dev@incubator.apache.org Delivered-To: mailing list mesos-dev@incubator.apache.org Received: (qmail 48830 invoked by uid 99); 20 Mar 2013 00:43:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Mar 2013 00:43:15 +0000 Date: Wed, 20 Mar 2013 00:43:15 +0000 (UTC) From: "Vinod Kone (JIRA)" To: mesos-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (MESOS-305) Inform the framework about a master failover MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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