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 "Sandy Ryza (JIRA)" <ji...@apache.org> on 2014/02/25 00:00:24 UTC
[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use
of CapacityScheduler
[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910944#comment-13910944 ]
Sandy Ryza commented on YARN-1760:
----------------------------------
A couple nits:
* The same configuration is used for all the tests. If the goal is to only use the capacity scheduler for a couple tests, then it should be instantiated in setup()
{code}
+ configuration.set(YarnConfiguration.RM_SCHEDULER,
+ "org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler");
{code}
It looks like this goes over 80 characters. Also, probably better to use CapacityScheduler.class.getName().
> TestRMAdminService assumes the use of CapacityScheduler
> -------------------------------------------------------
>
> Key: YARN-1760
> URL: https://issues.apache.org/jira/browse/YARN-1760
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Trivial
> Labels: test
> Attachments: yarn-1760-1.patch
>
>
> YARN-1611 adds TestRMAdminService which assumes the use of CapacityScheduler.
> {noformat}
> java.lang.ClassCastException: org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler cannot be cast to org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler
> at org.apache.hadoop.yarn.server.resourcemanager.TestRMAdminService.testAdminRefreshQueuesWithFileSystemBasedConfigurationProvider(TestRMAdminService.java:115)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)