Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 20 Feb 2015 11:58:13 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12776187.1424358575000.94343.1424433493559@Atlassian.JIRA>
In-Reply-To: <JIRA.12776187.1424358575000@Atlassian.JIRA>
References: <JIRA.12776187.1424358575000@Atlassian.JIRA>
 <JIRA.12776187.1424358575189@arcas>
Subject: [jira] [Commented] (YARN-3226) UI changes for decommissioning node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sunil G commented on YARN-3226:
-------------------------------

Yes. I also feel we could remove some dead tabs, and then add the new tab called "state".
Filtering mechanism can be added in a new tab which can just show decommissioned nodes. I will check on this line and work on same line. Thank you.

> UI changes for decommissioning node
> -----------------------------------
>
>                 Key: YARN-3226
>                 URL: https://issues.apache.org/jira/browse/YARN-3226
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Sunil G
>
> Some initial thought is:
> decommissioning nodes should still show up in the active nodes list since they are still running containers. 
> A separate decommissioning tab to filter for those nodes would be nice, although I suppose users can also just use the jquery table to sort/search for
> nodes in that state from the active nodes list if it's too crowded to add yet another node
> state tab (or maybe get rid of some effectively dead tabs like the reboot state tab).


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