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 4A3BE9911 for ; Thu, 10 Nov 2011 16:45:17 +0000 (UTC) Received: (qmail 1416 invoked by uid 500); 10 Nov 2011 16:45:17 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 1392 invoked by uid 500); 10 Nov 2011 16:45:17 -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 1382 invoked by uid 99); 10 Nov 2011 16:45:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2011 16:45:17 +0000 X-ASF-Spam-Status: No, hits=-2001.2 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; Thu, 10 Nov 2011 16:45:14 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 0D6314A73C for ; Thu, 10 Nov 2011 16:44:53 +0000 (UTC) Date: Thu, 10 Nov 2011 16:44:53 +0000 (UTC) From: "jiraposter@reviews.apache.org (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <881116244.17954.1320943493056.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1635405981.56158.1320335372240.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3341) Enhance logging of initalized queue limit values 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-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147813#comment-13147813 ] jiraposter@reviews.apache.org commented on MAPREDUCE-3341: ---------------------------------------------------------- ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/2775/#review3157 ----------------------------------------------------------- Ship it! looks good to me +1 (non-binding) - Robert On 2011-11-09 22:14:25, Anupam Seth wrote: bq. bq. ----------------------------------------------------------- bq. This is an automatically generated e-mail. To reply, visit: bq. https://reviews.apache.org/r/2775/ bq. ----------------------------------------------------------- bq. bq. (Updated 2011-11-09 22:14:25) bq. bq. bq. Review request for Robert Evans and Jonathan Eagles. bq. bq. bq. Summary bq. ------- bq. bq. Enhance logging for queues in capacity scheduler bq. bq. bq. This addresses bug MAPREDUCE-3341. bq. https://issues.apache.org/jira/browse/MAPREDUCE-3341 bq. bq. bq. Diffs bq. ----- bq. bq. branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java 1199955 bq. bq. Diff: https://reviews.apache.org/r/2775/diff bq. bq. bq. Testing bq. ------- bq. bq. bq. Thanks, bq. bq. Anupam bq. bq. > Enhance logging of initalized queue limit values > ------------------------------------------------ > > Key: MAPREDUCE-3341 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3341 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Anupam Seth > Assignee: Anupam Seth > Attachments: MAPREDUCE-3341-branch_0_23.patch, MAPREDUCE-3341-branch_0_23.patch > > > Currently the RM log shows only a partial set of the limits that are configured when a queue is initialized / reinitialized. > For example, this is what is currently shown in the RM log for an initialized queue: > # INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Initializing > default, capacity=0.25, asboluteCapacity=0.25, maxCapacity=25.0, asboluteMaxCapacity=0.25, userLimit=100, > userLimitFactor=20.0, maxApplications=2500, maxApplicationsPerUser=50000, state=RUNNING, > acls=ADMINISTER_QUEUE:*SUBMIT_JOB:*ADMINISTER_JOBS:* > Breaking down the line above, shows: > capacity=0.25 > asboluteCapacity=0.25 > maxCapacity=25.0 > asboluteMaxCapacity=0.25 > userLimit=100 > userLimitFactor=20.0 > maxApplications=2500 > maxApplicationsPerUser=50000 > It might be nice if we could include more information such as maxActiveApplications, maxActiveApplicationsPerUser, utilization, and usedCapacity along with information on how each of these is computed (i.e. formulae used) (Thanks to Phil Su for requesting this). -- 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