Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 18 May 2015 03:30:00 +0000 (UTC)
From: "sandflee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12830490.1431868266000.139701.1431919800252@Atlassian.JIRA>
In-Reply-To: <JIRA.12830490.1431868266000@Atlassian.JIRA>
References: <JIRA.12830490.1431868266000@Atlassian.JIRA>
 <JIRA.12830490.1431868266818@arcas>
Subject: [jira] [Commented] (YARN-3668) Long run service shouldn't be killed
 even if Yarn crashed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sandflee commented on YARN-3668:
--------------------------------

I don't want the service to terminated if AM goes down, yarn will also restart AM until it is launched successfully. 
By outside ways we could detect this situation and replace a new AM jar.

> Long run service shouldn't be killed even if Yarn crashed
> ---------------------------------------------------------
>
>                 Key: YARN-3668
>                 URL: https://issues.apache.org/jira/browse/YARN-3668
>             Project: Hadoop YARN
>          Issue Type: Wish
>            Reporter: sandflee
>
> For long running service, it shouldn't be killed even if all yarn component crashed, with RM work preserving and NM restart, yarn could take over applications again.


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