Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 13 Sep 2016 17:49:20 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13004140.1473600198000.561739.1473788960674@Atlassian.JIRA>
In-Reply-To: <JIRA.13004140.1473600198000@Atlassian.JIRA>
References: <JIRA.13004140.1473600198000@Atlassian.JIRA> <JIRA.13004140.1473600198694@arcas>
Subject: [jira] [Comment Edited] (YARN-5635) Better handling when bad script
 is configured as Node's HealthScript
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 13 Sep 2016 17:49:23 -0000


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

Allen Wittenauer edited comment on YARN-5635 at 9/13/16 5:49 PM:
-----------------------------------------------------------------

bq. does that hold true for even making it an option via a configuration setting?

Yes.

I don't know how many ways I can tell you that depending upon on an exit code here is extremely dangerous and has proven to be unreliable due to the constantly shifting nature of the state of the node on busy clusters. Throw in all of this "magically expanding/shrinking" task resource management bits that have gone in, and the situation gets even worse.

Besides, if you REALLY REALLY REALLY want to do this, all you need to do is wrap your existing health check in something else that, upon failure, prints the ERROR message.  


was (Author: aw):
bq. does that hold true for even making it an option via a configuration setting?

Yes.

I don't know how many ways I can tell you that depending upon on an error code here is extremely dangerous and has proven to be unreliable due to the constantly shifting nature of the state of the node on busy clusters. Throw in all of this "magically expanding/shrinking" task resource management bits that have gone in, and the situation gets even worse.

Besides, if you REALLY REALLY REALLY want to do this, all you need to do is wrap your existing health check in something else that, upon failure, prints the ERROR message.  

> Better handling when bad script is configured as Node's HealthScript
> --------------------------------------------------------------------
>
>                 Key: YARN-5635
>                 URL: https://issues.apache.org/jira/browse/YARN-5635
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>            Assignee: Yufei Gu
>
> Earlier fix to YARN-5567 is reverted because its not ideal to get the whole cluster down because of a bad script. At the same time its important to report that script is erroneous which is configured as node health script as it might miss to detect bad health of a node.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org