Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 2 Dec 2015 21:17:10 +0000 (UTC)
From: "Daniel Templeton (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12917728.1449090227000.251327.1449091030949@Atlassian.JIRA>
In-Reply-To: <JIRA.12917728.1449090227000@Atlassian.JIRA>
References: <JIRA.12917728.1449090227000@Atlassian.JIRA>
 <JIRA.12917728.1449090227511@arcas>
Subject: [jira] [Commented] (YARN-4413) Nodes in the includes list should
 not be listed as decommissioned in the UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Templeton commented on YARN-4413:
----------------------------------------

Yes.  The refresh marks nodes newly added to the excludes list as decommissioned, but it doesn't do anything for nodes newly added to the includes list.

> Nodes in the includes list should not be listed as decommissioned in the UI
> ---------------------------------------------------------------------------
>
>                 Key: YARN-4413
>                 URL: https://issues.apache.org/jira/browse/YARN-4413
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> If I decommission a node and then move it from the excludes list back to the includes list, but I don't restart the node, the node will still be listed by the web UI as decomissioned until either the NM or RM is restarted.  Ideally, removing the node from the excludes list and putting it back into the includes list should cause the node to be reported as shutdown instead.
> CC [~kshukla]


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