[
https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329194#comment-14329194
]
Hadoop QA commented on YARN-2083:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12650950/YARN-2083-3.patch
against trunk revision a64dd3d.
{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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6682//console
This message is automatically generated.
> In fair scheduler, Queue should not been assigned more containers when its
> usedResource had reach the maxResource limit
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-2083
> URL: https://issues.apache.org/jira/browse/YARN-2083
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.3.0
> Reporter: Yi Tian
> Labels: fairscheduler
> Attachments: YARN-2083-1.patch, YARN-2083-2.patch, YARN-2083-3.patch,
> YARN-2083.patch
>
>
> In fair scheduler, FSParentQueue and FSLeafQueue do an
> assignContainerPreCheck to guaranty this queue is not over its limit.
> But the fitsIn function in Resource.java did not return false when the
> usedResource equals the maxResource.
> I think we should create a new Function "fitsInWithoutEqual" instead of
> "fitsIn" in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
