Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Thu, 16 Jan 2014 22:57:20 +0000 (UTC)
From: "Bill Farner (JIRA)" <jira@apache.org>
To: dev@aurora.incubator.apache.org
Message-ID: <JIRA.12689382.1389911468071.19645.1389913040322@arcas>
In-Reply-To: <JIRA.12689382.1389911468071@arcas>
References: <JIRA.12689382.1389911468071@arcas>
Subject: [jira] [Commented] (AURORA-45) Scheduler should wait for registered
 to be called before attempting to invoke driver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AURORA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874106#comment-13874106 ] 

Bill Farner commented on AURORA-45:
-----------------------------------

Nope, i explicitly left this behavior in tact during that refactor to minimally impact tests.  The fix is trivial after that refactor, though.

> Scheduler should wait for registered to be called before attempting to invoke driver
> ------------------------------------------------------------------------------------
>
>                 Key: AURORA-45
>                 URL: https://issues.apache.org/jira/browse/AURORA-45
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Bill Farner
>            Assignee: Bill Farner
>
> We have observed the scheduler attempting to kill tasks before {{registered()}} had been called. This resulted in the driver dropping those attempts on the floor. Since the driver didn't signal failure to the scheduler (but instead logged an error) the scheduler wrote a KILLING state transition to the replicated log and signaled success to the client. Since the {{killTasks}} message was never sent the task timed out and the task continued to run until the GC executor reconciled state.


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