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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/02/06 23:54:35 UTC

[jira] [Commented] (YARN-281) Add a test for YARN Schedulers' MAXIMUM_ALLOCATION limits

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

Wangda Tan commented on YARN-281:
---------------------------------

I think this may not need since we already have tests in TestSchedulerUitls, it will verify minimum/maximum resource normalization/verification. And SchedulerUtil runs before scheduler can see such resource requests.

Resolved it as won't fix.

> Add a test for YARN Schedulers' MAXIMUM_ALLOCATION limits
> ---------------------------------------------------------
>
>                 Key: YARN-281
>                 URL: https://issues.apache.org/jira/browse/YARN-281
>             Project: Hadoop YARN
>          Issue Type: Test
>          Components: scheduler
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Assignee: Wangda Tan
>              Labels: test
>
> We currently have tests that test MINIMUM_ALLOCATION limits for FifoScheduler and the likes, but no test for MAXIMUM_ALLOCATION yet. We should add a test to prevent regressions of any kind on such limits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)