Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 14 Aug 2013 04:58:48 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12635476.1362535722099.61517.1376456328708@arcas>
In-Reply-To: <JIRA.12635476.1362535722099@arcas>
References: <JIRA.12635476.1362535722099@arcas>
Subject: [jira] [Commented] (YARN-451) Add more metrics to RM page
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli commented on YARN-451:
----------------------------------------------

Agreed about having it on the listing page, but that page is already dense. Have to do some basic UI design.

Again, like I mentioned, Hadoop-1 was different as number of maps, reduces doesn't change after job starts. Whereas in Hadoop-2, memory/cores allocated slowly increases over time , so it may or may not be of much use. I am ambivalent about adding it.
                
> Add more metrics to RM page
> ---------------------------
>
>                 Key: YARN-451
>                 URL: https://issues.apache.org/jira/browse/YARN-451
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.0.3-alpha
>            Reporter: Lohit Vijayarenu
>            Priority: Minor
>
> ResourceManager webUI shows list of RUNNING applications, but it does not tell which applications are requesting more resource compared to others. With cluster running hundreds of applications at once it would be useful to have some kind of metric to show high-resource usage applications vs low-resource usage ones. At the minimum showing number of containers is good option.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira