hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4935) TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler
Date Mon, 11 Apr 2016 00:06:25 GMT

    [ https://issues.apache.org/jira/browse/YARN-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234365#comment-15234365

Karthik Kambatla commented on YARN-4935:

If the test is capacity scheduler specific, should it be in the capacity scheduler tests?
If the goal is to check the YarnClient behavior, may be the name of the test should reflect
it is testing only capacity scheduler? 

> TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler
> ----------------------------------------------------------------
>                 Key: YARN-4935
>                 URL: https://issues.apache.org/jira/browse/YARN-4935
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.8.0
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>         Attachments: YARN-4935.001.patch
> This test case introduced by YARN-3131 works well on CapacityScheduler but not on FairScheduler,
since CS doesn't allow dynamically create a queue, while FS supports it. So if you give a
random queue name, CS will reject it, but FS will create a new queue for it by default. 
> One simple solution is to specific CS in this test case. /cc [~lichangleo]. I was thinking
about creating another test case for FS. But for the code introduced by YARN-3131, it may
be not necessary.

This message was sent by Atlassian JIRA

View raw message