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 "Thomas Graves (JIRA)" <ji...@apache.org> on 2013/09/06 20:28:02 UTC

[jira] [Comment Edited] (YARN-1153) CapacityScheduler queue elasticity is not working

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

Thomas Graves edited comment on YARN-1153 at 9/6/13 6:26 PM:
-------------------------------------------------------------

sorry so why is this a bug?  Its working as designed.  If we want to change that, we should make this an enhancement request.

the "fix" is change your config
                
      was (Author: tgraves):
    sorry so why is this a bug?  Its working as designed.  If we want to change that, we should make this an enhancement request.
                  
> CapacityScheduler queue elasticity is not working
> -------------------------------------------------
>
>                 Key: YARN-1153
>                 URL: https://issues.apache.org/jira/browse/YARN-1153
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Jian He
>
> Configured 2 queues one with 25% capacity and the other with 75% capacity,
> and both has 100% max-capacity.
> Submit only 1 application to whichever queue. Ideally, it should take use of 100% cluster's resources, but it's not.
> Tested this on single node cluster using DefaultResourceCalculator.

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