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

Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/05/03 03:47:06 UTC

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

     [ https://issues.apache.org/jira/browse/YARN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli resolved YARN-148.
------------------------------------------
    Resolution: Invalid

I don't see this issue anymore, seems like it got resolved along the way.

Resolving this old ticket.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)