[ https://issues.apache.org/jira/browse/MAPREDUCE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420893#comment-13420893 ]
Robert Joseph Evans commented on MAPREDUCE-3893: ------------------------------------------------ The latest set of changes look good to me +1. > allow capacity scheduler configs maximum-applications and > maximum-am-resource-percent configurable on a per queue basis > ----------------------------------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-3893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Thomas Graves > Assignee: Thomas Graves > Priority: Critical > Attachments: MAPREDUCE-3893-1.txt, MAPREDUCE-3893.patch > > > The capacity scheduler configs for maximum-applications and > maximum-am-resource-percent are currently configured globally and then made > proportional to each queue based on its capacity. There are times when this > may not work well. some exampless - if you have a queue that is running on > uberAM jobs, the jobs a queue is running always has a small number of > containers, and then you have the opposite where in a queue with very small > capacity, you may want to limit the am resources even more so you don't end > up deadlocked with all your capacity being used for app masters. > I think we should make those configurable on a per queue basis. -- 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