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 D785517F58 for ; Fri, 6 Feb 2015 18:11:27 +0000 (UTC) Received: (qmail 86160 invoked by uid 500); 6 Feb 2015 18:11:23 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 86033 invoked by uid 500); 6 Feb 2015 18:11:23 -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 86023 invoked by uid 99); 6 Feb 2015 18:11:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2015 18:11:22 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=FSL_HELO_BARE_IP_2,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of xgong@hortonworks.com designates 64.78.52.187 as permitted sender) Received: from [64.78.52.187] (HELO relayvx12c.securemail.intermedia.net) (64.78.52.187) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2015 18:10:55 +0000 Received: from emg-ca-1-2 (localhost [127.0.0.1]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id 295A653E57 for ; Fri, 6 Feb 2015 10:10:53 -0800 (PST) Subject: Re: Hadoop Node Failure Detection MIME-Version: 1.0 x-echoworx-emg-received: Fri, 6 Feb 2015 10:10:53.158 -0800 x-echoworx-msg-id: a87fe747-4fc7-4eba-806d-125c6d350ca4 x-echoworx-action: delivered Received: from 10.254.155.17 ([10.254.155.17]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 897 for ; Fri, 6 Feb 2015 10:10:53 -0800 (PST) Received: from MBX080-W4-CO-2.exch080.serverpod.net (unknown [10.224.117.102]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id EDC6B53E57 for ; Fri, 6 Feb 2015 10:10:52 -0800 (PST) Received: from MBX080-W4-CO-2.exch080.serverpod.net (10.224.117.102) by MBX080-W4-CO-2.exch080.serverpod.net (10.224.117.102) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 6 Feb 2015 10:10:50 -0800 Received: from MBX080-W4-CO-2.exch080.serverpod.net ([10.224.117.102]) by mbx080-w4-co-2.exch080.serverpod.net ([10.224.117.102]) with mapi id 15.00.1044.021; Fri, 6 Feb 2015 10:10:50 -0800 From: Xuan Gong To: "user@hadoop.apache.org" Thread-Topic: Hadoop Node Failure Detection Thread-Index: AQHQQjdVlgDaj1UqoUaMt24U30wznZzj7AmA Date: Fri, 6 Feb 2015 18:10:50 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [50.46.180.171] x-source-routing-agent: Processed Content-Type: multipart/alternative; boundary="_000_D0FA43133417Dxgonghortonworkscom_" X-Virus-Checked: Checked by ClamAV on apache.org --_000_D0FA43133417Dxgonghortonworkscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hey, Telles: You can simply decrease the NM expiry-interval. The default value is 5 mi= ns. You can config nm.liveness-monitor.expiry-interval-ms (in millisecond)i= n yarn-site.xml Thanks Xuan Gong From: Telles Nobrega > Reply-To: "user@hadoop.apache.org" > Date: Friday, February 6, 2015 at 10:03 AM To: "user@hadoop.apache.org" > Subject: Hadoop Node Failure Detection Hi, hadoop takes a while to "notice" that a node is gone right? I'm using hadoop 2.6.0 and I would like to change this detection time for e= xperience porpuse, which configuration should I change and where? Thanks --_000_D0FA43133417Dxgonghortonworkscom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Hey, Telles:

  You can simply decrease t= he NM expiry-interval. The default value is 5 mins. You can config nm.liveness-monitor.expi= ry-interval-ms (in millisecond)in yarn-site.xml


Thanks


Xuan Gong


From: Telles Nobrega <tellesnobrega@gmail.com>
Reply-To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Date: Friday, February 6, 2015 at 1= 0:03 AM
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Subject: Hadoop Node Failure Detect= ion

Hi, hadoop takes a while to "notice" that a node is gone rig= ht?

I'm using hadoop 2.6.0 and I would like to change this detection time = for experience porpuse, which configuration should I change and where?

Thanks
--_000_D0FA43133417Dxgonghortonworkscom_--