[
https://issues.apache.org/jira/browse/YARN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-148:
-----------------------------------------
Issue Type: Improvement (was: Bug)
> CapacityScheduler shouldn't explicitly need YarnConfiguration
> -------------------------------------------------------------
>
> Key: YARN-148
> URL: https://issues.apache.org/jira/browse/YARN-148
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
>
> This was done in MAPREDUCE-3773. None of our service APIs warrant
> YarnConfiguration. We affect the proper loading of yarn-site.xml by
> explicitly creating YarnConfiguration in all the main classes -
> ResourceManager, NodeManager etc.
> Due to this extra dependency, tests are failing, see
> https://builds.apache.org/job/PreCommit-YARN-Build/74//testReport/org.apache.hadoop.yarn.client/TestYarnClient/testClientStop/.
--
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
