[
https://issues.apache.org/jira/browse/MAPREDUCE-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192298#comment-13192298
]
Nathan Roberts commented on MAPREDUCE-3683:
-------------------------------------------
I'm fine with doing things in a separate jira, but doesn't this whole issue get
much simpler if we can get rid of of MAX_FLOAT?
For example, my understanding of the current patch is that a configuration like:
a (25,UNDEFINED)
a.a1 (50, 50)
will let a job submitted to a.a1 consume the entire grid. This doesn't seem
intuitive to me in that we ignored the maxcap setting of a.a1. Since the parent
is UNDEFINED, computeAbsoluteMaxCapacity will return Float.MAX_VALUE. Am I
missing something there?
> Capacity scheduler LeafQueues maximum capacity calculation issues
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-3683
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3683
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Thomas Graves
> Assignee: Arun C Murthy
> Priority: Blocker
> Attachments: MAPREDUCE-3683.patch, MAPREDUCE-3683.patch
>
>
> In the Capacity scheduler if you configure the queues to be hierarchical
> where you have root -> parent queue -> leaf queue, the leaf queue doesn't
> take into account its parents maximum capacity when calculate its own maximum
> capacity, instead it seems to use the parents capacity. Looking at the code
> its using the parents absoluteCapacity and I think it should be using the
> parents absoluteMaximumCapacity.
> It also seems to only use the parents capacity in the leaf queues max
> capacity calculation when the leaf queue has a max capacity configured. If
> the leaf queues maximum-capacity is not configured, then it can use 100% of
> the cluster.
--
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
