Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Sat, 11 Apr 2015 21:07:12 +0000 (UTC)
From: "Stephan Erb (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.12820348.1428786389000.64781.1428786432094@Atlassian.JIRA>
In-Reply-To: <JIRA.12820348.1428786389000@Atlassian.JIRA>
References: <JIRA.12820348.1428786389000@Atlassian.JIRA>
 <JIRA.12820348.1428786389333@arcas>
Subject: [jira] [Created] (AURORA-1275) Don't delay kill sequence when HTTP
 teardown signal could not be dispatched
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Stephan Erb created AURORA-1275:
-----------------------------------

             Summary: Don't delay kill sequence when HTTP teardown signal could not be dispatched
                 Key: AURORA-1275
                 URL: https://issues.apache.org/jira/browse/AURORA-1275
             Project: Aurora
          Issue Type: Story
          Components: Executor, Thermos
            Reporter: Stephan Erb
            Assignee: Stephan Erb


The Thermos task runner performs a kill escalation sequence by dispatching calls to the HTTP endpoints /quitquitquit and /abortabortabort before stopping a task for good. After each of these calls it waits for 5 seconds.

The runner should not perform the waiting when the corresponding shutdown request could not be dispatched. 

Advantages:

* Services which use a health port but don't implement /qqq and /aaa are not taxed by a total of 10 seconds waiting time for each kill operation
* The whole system is faster to react when services are meant to be restarted due to failing health checks. Failing health checks often imply an application is not responding at all, including the endpoints /qqq and /aaa


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)