[ https://issues.apache.org/jira/browse/MAPREDUCE-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated MAPREDUCE-3681: ------------------------------------- Priority: Critical (was: Blocker) Good catch Thomas. Thankfully this isn't super-critical because 'usedCapacity' is used nowhere other than displaying queue-stats to clients i.e. it doesn't runtime behaviour of the CapacityScheduler. I'll fix this. > capacity scheduler LeafQueues calculate used capacity wrong > ----------------------------------------------------------- > > Key: MAPREDUCE-3681 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3681 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Thomas Graves > Assignee: Arun C Murthy > Priority: Critical > > 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 > calculate the used capacity properly. It seems to be using the entire cluster > memory rather then its parents memory capacity. > In updateResource in LeafQueue: > setUsedCapacity( > usedResources.getMemory() / (clusterResource.getMemory() * capacity)); > I think the clusterResource.getMemory() should be something like > getParentsMemory(). -- 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