[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208834#comment-14208834 ]
Hadoop QA commented on YARN-2811: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12681143/YARN-2811.v7.patch against trunk revision 782abbb. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/5828//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5828//console This message is automatically generated. > Fair Scheduler is violating max memory settings in 2.4 > ------------------------------------------------------ > > Key: YARN-2811 > URL: https://issues.apache.org/jira/browse/YARN-2811 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 2.4.0 > Reporter: Siqi Li > Assignee: Siqi Li > Attachments: YARN-2811.v1.patch, YARN-2811.v2.patch, > YARN-2811.v3.patch, YARN-2811.v4.patch, YARN-2811.v5.patch, > YARN-2811.v6.patch, YARN-2811.v7.patch > > > This has been seen on several queues showing the allocated MB going > significantly above the max MB and it appears to have started with the 2.4 > upgrade. It could be a regression bug from 2.0 to 2.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)