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 E8B1C76D6 for ; Fri, 14 Oct 2011 09:34:39 +0000 (UTC) Received: (qmail 54096 invoked by uid 500); 14 Oct 2011 09:34:39 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 54068 invoked by uid 500); 14 Oct 2011 09:34:39 -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 54049 invoked by uid 99); 14 Oct 2011 09:34:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 09:34:39 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,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; Fri, 14 Oct 2011 09:34:33 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 37418307D4E for ; Fri, 14 Oct 2011 09:34:12 +0000 (UTC) Date: Fri, 14 Oct 2011 09:34:12 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1644751822.13377.1318584852227.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1003352966.50564.1316611750177.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3059) QueueMetrics do not have metrics for aggregate containers-allocated and aggregate containers-released 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-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127393#comment-13127393 ] Hadoop QA commented on MAPREDUCE-3059: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12499000/MAPREDUCE-3059-1.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 20 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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/1017//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1017//console This message is automatically generated. > QueueMetrics do not have metrics for aggregate containers-allocated and aggregate containers-released > ----------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-3059 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3059 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Karam Singh > Assignee: Devaraj K > Priority: Blocker > Fix For: 0.23.0 > > Attachments: MAPREDUCE-3059-1.patch, MAPREDUCE-3059.patch > > > QueueMetrics for ResourceManager do not have any metrics for aggregate containers-allocated and containers-released. > We need the aggregates of containers-allocated and containers-released to figure out the rate at which RM is dishing out containers. NodeManager do have containers-launched and container-released metrics, but this is not across all nodes; so to get the cluster level aggregate, we need to preprocess NM metrics from all nodes - which is troublesome. > Currently, we do have AllocatedContainers and PendingContainers which reflect the running containers given out to AMs, and containers waiting for allocation respectively. -- 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