Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 475AD10F38 for ; Sat, 8 Feb 2014 14:04:01 +0000 (UTC) Received: (qmail 26854 invoked by uid 500); 8 Feb 2014 14:03:53 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 26780 invoked by uid 500); 8 Feb 2014 14:03:52 -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 26772 invoked by uid 99); 8 Feb 2014 14:03:52 -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:03:52 +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.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Feb 2014 14:03:46 +0000 Received: by mail-ie0-f174.google.com with SMTP id tp5so2437676ieb.33 for ; Sat, 08 Feb 2014 06:03:26 -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=TmRTU0Lwllpo+QKLFI1EZVbmy6lKMkjDOorYB3m4asU=; b=SDPuU3+5GB2GXeJ/AF8w/9ijp0q+XOHmSDqpdRGyXyrDZzfxY9vUaB/YX6yG1W5pYM CNzu6ic5iLT8giSV5eeJg9V3sO4R7Ngyly7pMljfPpHgbjxCZ3TEdFc7x0687SQmAN2C TUjydcqLcGtD5RA4G98H3/nkr+g+1C0Gggpb6f5Bixt81SeoshteAJ8vaeb86fzewMeO J4nwltmnXzafqI/TSt6xgqqnExIMz9tVzOaQqPYgWQElf++rVFt70uO+tsWshAQ1/TJL XJTQ88GR8KOg5Kv0PRkfbfEN1dtdzn4OgdwUaQc19Zx5dGs3rGEOON0fjq30Zorj4EG8 Cp4Q== X-Gm-Message-State: ALoCoQlE3uVsaeggetqXPB6QUfgWG+opLswV9CEQooI5vNFCb4iarx4o74+kcOyQbKS4+lm1Zc5S X-Received: by 10.50.118.41 with SMTP id kj9mr5082248igb.37.1391868205909; Sat, 08 Feb 2014 06:03:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.61.97 with HTTP; Sat, 8 Feb 2014 06:03:04 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Sat, 8 Feb 2014 19:33:04 +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 Correction: Set it to 1 (For 1 max attempt), not 0. On Sat, Feb 8, 2014 at 7:31 PM, Harsh J wrote: > 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 -- Harsh J