[
https://issues.apache.org/jira/browse/YARN-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792821#comment-13792821
]
Sandy Ryza commented on YARN-1300:
----------------------------------
This is occurring because of YARN-1228. It used to be that fair-scheduler.xml
could house either hadoop-style configuration properties (e.g. for
yarn.scheduler.fair.assignmultiple) or the fair scheduler allocations
configuration. We changed it to only allow the latter, but
./hadoop-tools/hadoop-sls/src/test/resources/fair-scheduler.xml does the
former. We'll need to move the properties in it either into a yarn-site.xml or
into the code.
Updated the title of the JIRA to reflect this.
> SLS tests fail because conf puts yarn properties in fair-scheduler.xml
> ----------------------------------------------------------------------
>
> Key: YARN-1300
> URL: https://issues.apache.org/jira/browse/YARN-1300
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Ted Yu
>
> I was looking at
> https://builds.apache.org/job/PreCommit-YARN-Build/2165//testReport/org.apache.hadoop.yarn.sls/TestSLSRunner/testSimulatorRunning/
> I am able to reproduce the failure locally.
> I found that FairSchedulerConfiguration.getAllocationFile() doesn't read the
> yarn.scheduler.fair.allocation.file config entry from fair-scheduler.xml
> This leads to the following:
> {code}
> Caused by:
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.AllocationConfigurationException:
> Bad fair scheduler config file: top-level element not <allocations>
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.QueueManager.reloadAllocs(QueueManager.java:302)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.QueueManager.initialize(QueueManager.java:108)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.reinitialize(FairScheduler.java:1145)
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
