[ 
https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198946#comment-14198946
 ] 

Hadoop QA commented on YARN-2811:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12679606/YARN-2811.v1.patch
  against trunk revision bc80251.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5741//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
>
>
> 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)

Reply via email to