hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-177) CapacityScheduler - adding a queue while the RM is running has wacky results
Date Tue, 23 Oct 2012 18:43:13 GMT

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

Hadoop QA commented on YARN-177:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  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/119//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/119//console

This message is automatically generated.
> CapacityScheduler - adding a queue while the RM is running has wacky results
> ----------------------------------------------------------------------------
>                 Key: YARN-177
>                 URL: https://issues.apache.org/jira/browse/YARN-177
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Arun C Murthy
>            Priority: Critical
>             Fix For: 2.0.3-alpha, 0.23.5
>         Attachments: YARN-177.patch, YARN-177.patch, YARN-177.patch, YARN-177.patch
> Adding a queue to the capacity scheduler while the RM is running and then running a job
in the queue added results in very strange behavior.  The cluster Total Memory can either
decrease or increase.  We had a cluster where total memory decreased to almost 1/6th the capacity.
Running on a small test cluster resulted in the capacity going up by simply adding a queue
and running wordcount.  
> Looking at the RM logs, used memory can go negative but other logs show the number positive:
> 2012-10-21 22:56:44,796 [ResourceManager Event Processor] INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue:
assignedContainer queue=root usedCapacity=0.0375 absoluteUsedCapacity=0.0375 used=memory:
7680 cluster=memory: 204800
> 2012-10-21 22:56:45,831 [ResourceManager Event Processor] INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue:
completedContainer queue=root usedCapacity=-0.0225 absoluteUsedCapacity=-0.0225 used=memory:
-4608 cluster=memory: 204800

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message