Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 1 Dec 2015 19:18:11 +0000 (UTC)
From: "Daniel Templeton (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12917078.1448920747000.236356.1448997491044@Atlassian.JIRA>
In-Reply-To: <JIRA.12917078.1448920747000@Atlassian.JIRA>
References: <JIRA.12917078.1448920747000@Atlassian.JIRA>
 <JIRA.12917078.1448920747292@arcas>
Subject: [jira] [Updated] (YARN-4401) A failed app recovery should not
 prevent the RM from starting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Templeton updated YARN-4401:
-----------------------------------
    Attachment: YARN-4401.001.patch

Here's the basic idea of what I'm proposing.

> A failed app recovery should not prevent the RM from starting
> -------------------------------------------------------------
>
>                 Key: YARN-4401
>                 URL: https://issues.apache.org/jira/browse/YARN-4401
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Critical
>         Attachments: YARN-4401.001.patch
>
>
> There are many different reasons why an app recovery could fail with an exception, causing the RM start to be aborted.  If that happens the RM will fail to start.  Presumably, the reason the RM is trying to do a recovery is that it's the standby trying to fill in for the active.  Failing to come up defeats the purpose of the HA configuration.  Instead of preventing the RM from starting, a failed app recovery should log an error and skip the application.


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