Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 500CD10F2D for ; Sat, 8 Feb 2014 14:02:53 +0000 (UTC) Received: (qmail 22803 invoked by uid 500); 8 Feb 2014 14:02:45 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 22055 invoked by uid 500); 8 Feb 2014 14:02:38 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 22048 invoked by uid 99); 8 Feb 2014 14:02:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Feb 2014 14:02:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Feb 2014 14:02:30 +0000 Received: by mail-ie0-f182.google.com with SMTP id lx4so2441666iec.41 for ; Sat, 08 Feb 2014 06:02:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=NrDe93lQYQHI5bBp4zrcRJ8s+rMAC+fOmVQt7nKr36I=; b=T6hpbna7lTGatIVVdXFWHTV8fOMBd/xTQnvR93CrZu9yZ9Flwk5+eWnbggNjpka1u2 C4TCxIL4S0MyzR44M0HF3TqrbwDNha/ELtjUCzp3UqjEbRfcsFz8TI4/BcDDTdclReNm BBoP/FZCQjwsFUnPk4z1H5lsQKJiRLqhVQPEcxhh4dORcRPLKnMhzN+Zk2B/9RN9luBj 40pK4RJQ6ME9WMKDF8vp4FyhxwUrSnt4agmpjZfuFB6ioaWlXqn18w5gwzJwrxXbXEqx Sii9ZfxCLnddzKwsKDk3ZumktTi7kPK9qJE9m68Uk5ZEiG1FCWxaryzdLFtLFro/pBZf o+PQ== X-Gm-Message-State: ALoCoQnqg9i/HxVzLgklnZ9h8SBM1AygLjScbA+0viPAwBE5VFllTD8unNjlD+VezAOyChYiYzuL X-Received: by 10.50.102.99 with SMTP id fn3mr5154883igb.5.1391868130028; Sat, 08 Feb 2014 06:02:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.61.97 with HTTP; Sat, 8 Feb 2014 06:01:49 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Sat, 8 Feb 2014 19:31:49 +0530 Message-ID: Subject: Re: Can we avoid restarting of AM when it fails? To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org You can set http://hadoop.apache.org/docs/current/api/org/apache/hadoop/yarn/api/records/ApplicationSubmissionContext.html#setMaxAppAttempts(int) to 0, at a per-app level, to prevent any reattempts/recovery of your AM. For a cluster-wide effect instead, you can limit by overriding the default value of the RM property yarn.resourcemanager.am.max-retries in the RM's YarnConfiguration or yarn-site.xml. On Fri, Feb 7, 2014 at 5:24 PM, Krishna Kishore Bonagiri wrote: > 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 _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 -- Harsh J