[
https://issues.apache.org/jira/browse/YARN-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556957#comment-13556957
]
Thomas Graves commented on YARN-343:
------------------------------------
-1 was the value used in 1.X to also mean its disabled so we should support for
backwards compatibility. Its also documented in the 0.23/2.0 capacity
scheduler doc:
http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
> Capacity Scheduler maximum-capacity value -1 is invalid
> -------------------------------------------------------
>
> Key: YARN-343
> URL: https://issues.apache.org/jira/browse/YARN-343
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 0.23.6
> Reporter: Thomas Graves
>
> I tried to start the resource manager using the capacity scheduler with a
> particular queues maximum-capacity set to -1 which is supposed to disable it
> according to the docs but I got the following exception:
> java.lang.IllegalArgumentException: Illegal value of maximumCapacity -0.01
> used in call to setMaxCapacity for queue foo
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CSQueueUtils.checkMaxCapacity(CSQueueUtils.java:31)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.setupQueueConfigs(LeafQueue.java:220)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.<init>(LeafQueue.java:191)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:310)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:325)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:232)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:202)
--
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
