[ https://issues.apache.org/jira/browse/MAPREDUCE-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159662#comment-13159662 ]
Aaron T. Myers commented on MAPREDUCE-3483: ------------------------------------------- In some sense this seems like a specific case of the problem which was supposed to be addressed by MAPREDUCE-2324, right? > CapacityScheduler reserves container on same node as AM but can't ever use > due to never enough avail memory > ----------------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-3483 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3483 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Thomas Graves > Priority: Blocker > > Saw a case where a job was stuck trying to get reducers. The issue is the > capacity scheduler reserved a container on the same node as the application > master but there wasn't ever enough memory to run the reducer on that node. > Node total memory was 8G, Reducer needed 8G, AM was using 2G. This > particular job had 10 reducers and it was stuck waiting on the one because > the AM + reserved reducer memory was already over the queue limit. -- 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