hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes
Date Fri, 29 Mar 2013 10:41:26 GMT

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

Hudson commented on YARN-209:
-----------------------------

Integrated in Hadoop-Yarn-trunk #169 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/169/])
    YARN-209. Fix CapacityScheduler to trigger application-activation when the cluster capacity
changes. Contributed by Zhijie Shen. (Revision 1461773)

     Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1461773
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRM.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java

                
> Capacity scheduler doesn't trigger app-activation after adding nodes
> --------------------------------------------------------------------
>
>                 Key: YARN-209
>                 URL: https://issues.apache.org/jira/browse/YARN-209
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>            Reporter: Bikas Saha
>            Assignee: Zhijie Shen
>             Fix For: 2.0.5-beta
>
>         Attachments: YARN-209.1.patch, YARN-209.2.patch, YARN-209.3.patch, YARN-209.4.patch,
YARN-209-test.patch
>
>
> Say application A is submitted but at that time it does not meet the bar for activation
because of resource limit settings for applications. After that if more hardware is added
to the system and the application becomes valid it still remains in pending state, likely
forever.
> This might be rare to hit in real life because enough NM's heartbeat to the RM before
applications can get submitted. But a change in settings or heartbeat interval might make
it easier to repro. In RM restart scenarios, this will likely hit more if its implemented
by re-playing events and re-submitting applications to the scheduler before the RPC to NM's
is activated.

--
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

Mime
View raw message