[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nemon lou updated YARN-276: --------------------------- Attachment: YARN-276.patch Many test cases(both in YARN and MapReduce project) will fail because we have a more stringent AM used resource percent limit than before .These test cases fail to obtain an AM container.That's why i set the AM resource percent to 100% for both MiniYarnCluster and MockRM. May be i should change these failed test cases but there will be a lot of work to do.Or we can change default value in capacity-scheduler.xml both in project hadoop-yarn-server-tests and hadoop-yarn-server-resourcemanager. Thoughts? I need to dig more for changes in TestClientTokens.java as it's not clear to me now.So remove it first.Sorry for that. Other suggestiones has been acceptted. Uploading a temporary patch.(Setting the AM resource percent to 100% part has been removed,too) > Capacity Scheduler can hang when submit many jobs concurrently > -------------------------------------------------------------- > > Key: YARN-276 > URL: https://issues.apache.org/jira/browse/YARN-276 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Affects Versions: 3.0.0, 2.0.1-alpha > Reporter: nemon lou > Assignee: nemon lou > Labels: incompatible > Attachments: YARN-276.patch, YARN-276.patch, YARN-276.patch, > YARN-276.patch, YARN-276.patch, YARN-276.patch, YARN-276.patch, > YARN-276.patch, YARN-276.patch, YARN-276.patch, YARN-276.patch, > YARN-276.patch, YARN-276.patch, YARN-276.patch, YARN-276.patch, YARN-276.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In hadoop2.0.1,When i submit many jobs concurrently at the same time,Capacity > scheduler can hang with most resources taken up by AM and don't have enough > resources for tasks.And then all applications hang there. > The cause is that "yarn.scheduler.capacity.maximum-am-resource-percent" not > check directly.Instead ,this property only used for maxActiveApplications. > And maxActiveApplications is computed by minimumAllocation (not by Am > actually used). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira