[ https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213653#comment-14213653 ]
Hudson commented on YARN-2811: ------------------------------ FAILURE: Integrated in Hadoop-Mapreduce-trunk #1958 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1958/]) YARN-2811. In Fair Scheduler, reservation fulfillments shouldn't ignore max share (Siqi Li via Sandy Ryza) (sandy: rev 1a47f890ba3cb22b6262f47c1f1af2990559bb89) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java * hadoop-yarn-project/CHANGES.txt > In Fair Scheduler, reservation fulfillments shouldn't ignore max share > ---------------------------------------------------------------------- > > 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 > Fix For: 2.7.0 > > 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, YARN-2811.v8.patch, YARN-2811.v9.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)