Return-Path: 
 <yarn-issues-return-82551-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CB83D194CD
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue, 29 Mar 2016 13:56:26 +0000 (UTC)
Received: (qmail 442 invoked by uid 500); 29 Mar 2016 13:56:26 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 106 invoked by uid 500); 29 Mar 2016 13:56:26 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 99761 invoked by uid 99); 29 Mar 2016 13:56:25 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2016 13:56:25 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 89D492C1F62
	for <yarn-issues@hadoop.apache.org>; Tue, 29 Mar 2016 13:56:25 +0000 (UTC)
Date: Tue, 29 Mar 2016 13:56:25 +0000 (UTC)
From: "Fang Xie (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12954290.1459258808000.76214.1459259785560@Atlassian.JIRA>
In-Reply-To: <JIRA.12954290.1459258808000@Atlassian.JIRA>
References: <JIRA.12954290.1459258808000@Atlassian.JIRA>
 <JIRA.12954290.1459258808776@arcas>
Subject: [jira] [Updated] (YARN-4892) Job will be hung and can not be
 finished after resource manager restarting and enabling recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Fang Xie updated YARN-4892:
---------------------------
    Affects Version/s:     (was: 2.7.0)
                       2.7.1

> Job will be hung and can not be finished after resource manager restarting and enabling recovery
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4892
>                 URL: https://issues.apache.org/jira/browse/YARN-4892
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Fang Xie
>            Priority: Critical
>
> Enable resourcemanager recovery, set properties as below:
> <property>
>     <description>Enable RM to recover state after starting. If true, then
>     yarn.resourcemanager.store.class must be specified. </description>
>    <name>yarn.resourcemanager.recovery.enabled</name>
>    <value>true</value>
> </property>
> <property>
>     <description> </description>
>     <name>yarn.resourcemanager.store.class</name>
> <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore</value>
> </property>
> <property>
>     <description> </description>
>     <name>yarn.resourcemanager.fs.state-store.uri</name>
>     <value>hdfs://apple02:9000/rmstore</value>
> </property>
> run a distributedshell job, when job running, kill resourcemanager, and then restart resourcemanager, this job can not be finished and will be hung.
> Both fair-share and capacity scheduler have such issue.



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