You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/10/08 23:10:02 UTC

[jira] [Created] (YARN-148) CapacityScheduler shouldn't explicitly need YarnConfiguration

Vinod Kumar Vavilapalli created YARN-148:
--------------------------------------------

             Summary: CapacityScheduler shouldn't explicitly need YarnConfiguration
                 Key: YARN-148
                 URL: https://issues.apache.org/jira/browse/YARN-148
             Project: Hadoop YARN
          Issue Type: Bug
            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