You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/01/29 12:46:10 UTC
[jira] [Commented] (YARN-1631) Container allocation issue in
Leafqueue assignContainers()
[ https://issues.apache.org/jira/browse/YARN-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885267#comment-13885267 ]
Hadoop QA commented on YARN-1631:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12625843/Yarn-1631.2.patch
against trunk revision .
{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}. The javadoc tool did not generate any 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 1.3.9) 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/2957//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2957//console
This message is automatically generated.
> Container allocation issue in Leafqueue assignContainers()
> ----------------------------------------------------------
>
> Key: YARN-1631
> URL: https://issues.apache.org/jira/browse/YARN-1631
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.2.0
> Environment: SuSe 11 Linux
> Reporter: Sunil G
> Attachments: Yarn-1631.1.patch, Yarn-1631.2.patch
>
>
> Application1 has a demand of 8GB[Map Task Size as 8GB] which is more than Node_1 can handle.
> Node_1 has a size of 8GB and 2GB is used by Application1's AM.
> Hence reservation happened for remaining 6GB in Node_1 by Application1.
> A new job is submitted with 2GB AM size and 2GB task size with only 2 Maps to run.
> Node_2 also has 8GB capability.
> But Application2's AM cannot be launched in Node_2. And Application2 waits longer as only 2 Nodes are available in cluster.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)