hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (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 16:16:20 GMT

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

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

View raw message