You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/09/13 16:16:20 UTC
[jira] [Commented] (YARN-5635) Better handling when bad script is
configured as Node's HealthScript
[ https://issues.apache.org/jira/browse/YARN-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487633#comment-15487633 ]
Naganarasimha G R commented on YARN-5635:
-----------------------------------------
One of the approaches which was pointed in YARN-5567 :
{code}
NM can inform Healthy/UnHealthy/HealthValidationError, And this can be sent across Heartbeat to RM and RM can capture the state of this NM to be other than Running and UnHealthy (a New state). This can be displayed in the WebUI and also in the can be queried using ./yarn node -list -state
{code}
more thoughts on this approach ? cc/ [~yufeigu] & [~rchiang]
> 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
> Fix For: 3.0.0-alpha2
>
>
> 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