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 2012/10/22 20:46:19 UTC

[jira] [Assigned] (YARN-179) CapacityScheduler should not explicitly need YarnConfiguration.

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

Vinod Kumar Vavilapalli reassigned YARN-179:
--------------------------------------------

    Assignee: Vinod Kumar Vavilapalli
    
> CapacityScheduler should not explicitly need YarnConfiguration.
> ---------------------------------------------------------------
>
>                 Key: YARN-179
>                 URL: https://issues.apache.org/jira/browse/YARN-179
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>
> {{CapacityScheduler.setConf()}} mandates a YarnConfiguration. It doesn't need to, throughout all of YARN, components only depend on Configuration and depend on the callers to provide correct configuration.
> This is causing multiple tests to fail.

--
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