hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5635) Better handling when bad script is configured as Node's HealthScript
Date Tue, 13 Sep 2016 17:36:20 GMT

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

Allen Wittenauer commented on YARN-5635:
----------------------------------------

bq. except the newly defined error code which will mark the NodeManager as UNHEALTHY

No exceptions.  There is zero guarantee that the exit code of the script is the one you're
actually looking to catch.  For example, MAPREDUCE-6743 fixes a bug with the linking of nttest.
 The exit code on that prior to the fix? 127. 

Let me be absolutely crystal clear:  I'm going to -1 any patch that even thinks about treating
the exit code as a way to mark the NM as unhealthy.



> 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


Mime
View raw message