Return-Path: 
 <user-return-13641-apmail-hadoop-hdfs-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 41C2A100C0
	for <apmail-hadoop-hdfs-user-archive@minotaur.apache.org>;
 Fri,  7 Feb 2014 11:54:53 +0000 (UTC)
Received: (qmail 85044 invoked by uid 500); 7 Feb 2014 11:54:44 -0000
Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org
Received: (qmail 84183 invoked by uid 500); 7 Feb 2014 11:54:41 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 84164 invoked by uid 99); 7 Feb 2014 11:54:40 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Feb 2014 11:54:40 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of write2kishore@gmail.com
 designates 209.85.216.177 as permitted sender)
Received: from [209.85.216.177] (HELO mail-qc0-f177.google.com)
 (209.85.216.177)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Feb 2014 11:54:34 +0000
Received: by mail-qc0-f177.google.com with SMTP id i8so5574444qcq.22
        for <user@hadoop.apache.org>; Fri, 07 Feb 2014 03:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=nSMDZHaj3civZtISpLPzK9jHb16lDi9Ca33DGAje8Ws=;
        b=HcGE5+G1mgoO/hS55+BRbTSbT4YVbWKWT5qcfwc+YX9OUEjSZt0kqCxGusNSHGmH+W
         tWcFZXtUMOHJ5gcXbQrltqgdc0bUsjqRl/OBSsqb7oyDuVWFvHZB4kIy28ZB8O4Bt0vr
         NY10hG/4h7+PSsgrp9vzRuFH5nfBgGxZ6MCENBh6mvbuSP6mdxKCElRluS78ozyUH8gb
         8NnslFovBJ9E8xBeoMO7Cv90tUcr3iP2JD+sY5lzAxyffPb089WkwwUEg2sfs/I6y5iQ
         UBGZEH+nWy1Czz1kNjJkZJrs+GHl3+0oLDI37AfPy2o+hoNa+iY3LzzZVdJ8h7DbB8LG
         f3fA==
MIME-Version: 1.0
X-Received: by 10.140.83.212 with SMTP id j78mr19756392qgd.42.1391774053353;
 Fri, 07 Feb 2014 03:54:13 -0800 (PST)
Received: by 10.96.97.66 with HTTP; Fri, 7 Feb 2014 03:54:13 -0800 (PST)
Date: Fri, 7 Feb 2014 17:24:13 +0530
Message-ID: 
 <CAHg+sbNqCXkdaWfzwMcE+uk-YappyjDBMKt2=31VH+v4VpS_uw@mail.gmail.com>
Subject: Can we avoid restarting of AM when it fails?
From: Krishna Kishore Bonagiri <write2kishore@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001a11c124a00ed38c04f1cfa6f9
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c124a00ed38c04f1cfa6f9
Content-Type: text/plain; charset=ISO-8859-1

Hi,

   I am having some failure test cases where my Application Master is
supposed to fail. But when it fails it is again started with <appID>_02 .
Is there a way for me to avoid the second instance of the Application
Master getting started? Is it re-started automatically by the RM after the
first one failed?

Thanks,
Kishore

--001a11c124a00ed38c04f1cfa6f9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br><div>=A0 =A0I am having some failure test case=
s where my Application Master is supposed to fail. But when it fails it is =
again started with &lt;appID&gt;_02 . Is there a way for me to avoid the se=
cond instance of the Application Master getting started? Is it re-started a=
utomatically by the RM after the first one failed?</div>
<div><br></div><div>Thanks,</div><div>Kishore</div></div></div>

--001a11c124a00ed38c04f1cfa6f9--