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-3474) Add a way to let NM wait RM to come back, not kill running containers
Date Tue, 14 Apr 2015 17:20:12 GMT

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

Hadoop QA commented on YARN-3474:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision b5a0b24.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc 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
2.0.3) 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/7330//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7330//console

This message is automatically generated.

> Add a way to let NM wait RM to come back, not kill running containers
> ---------------------------------------------------------------------
>                 Key: YARN-3474
>                 URL: https://issues.apache.org/jira/browse/YARN-3474
>             Project: Hadoop YARN
>          Issue Type: New Feature
>    Affects Versions: 2.6.0
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>         Attachments: YARN-3474.01.patch
> When RM HA is enabled and active RM shuts down, standby RM will become active, recover
apps and attempts. Apps will not be affected. 
> If there are some cases or bugs that cause both RM could not start normally(e.g. [YARN-2340|https://issues.apache.org/jira/browse/YARN-2340];
RM could not connect with ZK well). NM will kill containers running on it when  it could not
heartbeat with RM for some time(max retry time is 15 mins by default). Then all apps will
be killed. 
> In production cluster, we might come across above cases and fixing these bugs might need
time more than 15 mins. In order to let apps not be affected and killed by NM, YARN admin
could set a flag(the flag is a znode '/wait-rm-to-come-back/cluster-id' in our solution) to
tell NM wait for RM to come back and not kill running containers. After fixing bugs and RM
start normally, clear the flag.

This message was sent by Atlassian JIRA

View raw message