You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Mayank Bansal (JIRA)" <ji...@apache.org> on 2012/06/21 23:47:42 UTC
[jira] [Commented] (MAPREDUCE-4360) Capacity Scheduler Hierarchical
leaf queue does not honur the max capacity of container queue
[ https://issues.apache.org/jira/browse/MAPREDUCE-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398892#comment-13398892 ]
Mayank Bansal commented on MAPREDUCE-4360:
------------------------------------------
Maximum capacity set on a container queue is not getting honored. For ex: If Queue A has Queue A1 and Queue A2 as child queues (leaf queues), and if max capacity is not set for the child queues and set only to the container queue (Queue A), then all the slots occupied by the jobs submitted to Queue A1 and Queue A2 should not exceed the maximum capacity configured for Queue A. However, it is not the case now. Tasks gets scheduled beyond Queue A's configured max capacity.
> Capacity Scheduler Hierarchical leaf queue does not honur the max capacity of container queue
> ---------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4360
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4360
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.22.1, trunk
> Reporter: Mayank Bansal
> Assignee: Mayank Bansal
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira