Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3398D9E23 for ; Mon, 16 Apr 2012 18:34:45 +0000 (UTC) Received: (qmail 62991 invoked by uid 500); 16 Apr 2012 18:34:43 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 62941 invoked by uid 500); 16 Apr 2012 18:34:43 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 62883 invoked by uid 99); 16 Apr 2012 18:34:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 18:34:43 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2012 18:34:42 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id B9A1A36E90F for ; Mon, 16 Apr 2012 18:34:22 +0000 (UTC) Date: Mon, 16 Apr 2012 18:34:22 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <66835389.29619.1334601262775.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1178989514.22151.1334327297438.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-4151) RM scheduler web page should filter apps to those that are relevant to scheduling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254883#comment-13254883 ] Hadoop QA commented on MAPREDUCE-4151: -------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12522811/MAPREDUCE-4151.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2228//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2228//console This message is automatically generated. > RM scheduler web page should filter apps to those that are relevant to scheduling > --------------------------------------------------------------------------------- > > Key: MAPREDUCE-4151 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4151 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2, webapps > Reporter: Jason Lowe > Assignee: Jason Lowe > Attachments: MAPREDUCE-4151.patch > > > On the ResourceManager's scheduler web page, the bottom of the page shows the apps block. When the cluster has run a lot of applications (e.g.: 10,000+) loading the apps table can take a long time, and that prolongs the plotting of the queue status which is the most interesting portion of the page. > If the user is bothering to go to the scheduler page, they're probably not interested in apps that are not affecting what the scheduler is doing (e.g.: FINISHED, FAILED, KILLED, etc.). Having the RM filter the apps for this page should significantly reduce the time it takes to load this page on the client, and it also helps reduce the amount of apps the user has to sift through when looking for the apps that are affecting what the scheduler is doing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira