[ https://issues.apache.org/jira/browse/YARN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472496#comment-13472496 ]
Alejandro Abdelnur commented on YARN-140: ----------------------------------------- Ahmed, overall looks good, there is one last change I'd do, where you add the check *if (capacity == UNDEFINED && queue.equals("root"))* it should be *if (capacity == UNDEFINED || queue.equals("root"))*, as for ROOT it should always be 100. > Add capacity-scheduler-default.xml to provide a default set of configurations > for the capacity scheduler. > --------------------------------------------------------------------------------------------------------- > > Key: YARN-140 > URL: https://issues.apache.org/jira/browse/YARN-140 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Reporter: Ahmed Radwan > Assignee: Ahmed Radwan > Attachments: YARN-140.patch, YARN-140_rev2.patch, > YARN-140_rev3.patch, YARN-140_rev4.patch, YARN-140_rev5_onlyForJenkins.patch, > YARN-140_rev5.patch, YARN-140_rev5_svn_mv.patch > > > When setting up the capacity scheduler users are faced with problems like: > {code} > FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error > starting ResourceManager > java.lang.IllegalArgumentException: Illegal capacity of -1 for queue root > {code} > Which basically arises from missing basic configurations, which in many > cases, there is no need to explicitly provide, and a default configuration > will be sufficient. For example, to address the error above, the user need to > add a capacity of 100 to the root queue. > So, we need to add a capacity-scheduler-default.xml, this will be helpful to > provide the basic set of default configurations required to run the capacity > scheduler. The user can still override existing configurations or provide new > ones in capacity-scheduler.xml. This is similar to *-default.xml vs > *-site.xml for yarn, core, mapred, hdfs, etc. -- 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