hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-281) Add a test for YARN Schedulers' MAXIMUM_ALLOCATION limits
Date Thu, 20 Dec 2012 18:37:19 GMT

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

Harsh J moved MAPREDUCE-4171 to YARN-281:
-----------------------------------------

          Component/s:     (was: mrv2)
                           (was: test)
                       scheduler
    Affects Version/s:     (was: 2.0.0-alpha)
                       2.0.0-alpha
                  Key: YARN-281  (was: MAPREDUCE-4171)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> 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: Harsh J
>              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 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

Mime
View raw message