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-433) When RM is catching up with node updates then it should not expire acquired containers
Date Fri, 31 Jul 2015 15:48:07 GMT

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

Hudson commented on YARN-433:
-----------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #270 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/270/])
YARN-433. When RM is catching up with node updates then it should not expire acquired containers.
Contributed by Xuan Gong (zxu: rev ab80e277039a586f6d6259b2511ac413e29ea4f8)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMNodeTransitions.java
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmcontainer/RMContainerImpl.java


> When RM is catching up with node updates then it should not expire acquired containers
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-433
>                 URL: https://issues.apache.org/jira/browse/YARN-433
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Bikas Saha
>            Assignee: Xuan Gong
>             Fix For: 2.8.0
>
>         Attachments: YARN-433.1.patch, YARN-433.2.patch, YARN-433.3.patch, YARN-433.4.patch
>
>
> RM expires containers that are not launched within some time of being allocated. The
default is 10mins. When an RM is not keeping up with node updates then it may not be aware
of new launched containers. If the expire thread fires for such containers then the RM can
expire them even though they may have launched.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message