Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 1 Feb 2012 14:13:05 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1914273263.2702.1328105585847.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1694971471.9289.1327959670699.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3762) Resource Manager fails to come
 up with default capacity scheduler configs.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on MAPREDUCE-3762:
-----------------------------------

Integrated in Hadoop-Mapreduce-0.23-Build #178 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/178/])
    Merge -c 1238987 from trunk to branch-0.23 to fix MAPREDUCE-3762. Fixed default CapacityScheduler configs.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1238989
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/resources/capacity-scheduler.xml

                
> Resource Manager fails to come up with default capacity scheduler configs.
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3762
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3762
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>            Priority: Critical
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3762.patch
>
>
> Thanks to [~harip] for pointing out the issue. This is the stack trace for bringing up RM with default CS configs:
> {code}
> java.lang.IllegalArgumentException: Illegal value  of maximumCapacity -0.01 used in call to setMaxCapacity for queue default
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CSQueueUtils.checkMaxCapacity(CSQueueUtils.java:28)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.setupQueueConfigs(LeafQueue.java:210)
>         at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.<init>(LeafQueue.java:184)
> {code}

--
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