[
https://issues.apache.org/jira/browse/YARN-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792765#comment-13792765
]
Ted Yu commented on YARN-1300:
------------------------------
FairSchedulerConfiguration.getAllocationFile() should read the value for
yarn.scheduler.fair.allocation.file config entry and open that for the return
value.
Is that what you were planning in YARN-1270 ?
> FairScheduler fails to start due to using incorrect allocation file
> -------------------------------------------------------------------
>
> 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)
