Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 24 Apr 2013 00:55:15 +0000 (UTC)
From: "Siddharth Wagle (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12644256.1366764827627.212885.1366764915793@arcas>
In-Reply-To: <JIRA.12644256.1366764827627@arcas>
References: <JIRA.12644256.1366764827627@arcas>
Subject: [jira] [Updated] (AMBARI-2010) Tasks do not timeout for failed
 hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Wagle updated AMBARI-2010:
------------------------------------

    Attachment: AMBARI-2010.patch
    
> Tasks do not timeout for failed hosts
> -------------------------------------
>
>                 Key: AMBARI-2010
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2010
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.3.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2010.patch
>
>
> We have seen that the tasks do not timeout within X minutes, where X is a predictable number like 10 minutes. This becomes relevant when task are created for dead nodes.
> Example, I have killed a host after registration and then hit Deploy for that host. Since the host is unreachable, we depend on task timeout to clean the pending actions, this happens but takes a very long time.
> One possible fix is to fast fail tasks for hosts in UNKNOWN state

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