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 2ADD510EF0 for ; Tue, 4 Mar 2014 12:55:20 +0000 (UTC) Received: (qmail 40707 invoked by uid 500); 4 Mar 2014 12:55:11 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 40270 invoked by uid 500); 4 Mar 2014 12:55:10 -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 40262 invoked by uid 99); 4 Mar 2014 12:55:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 12:55:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of john.lilley@redpoint.net designates 206.225.164.218 as permitted sender) Received: from [206.225.164.218] (HELO hub021-nj-3.exch021.serverdata.net) (206.225.164.218) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 12:55:01 +0000 Received: from MBX021-E3-NJ-2.exch021.domain.local ([10.240.4.78]) by HUB021-NJ-3.exch021.domain.local ([10.240.4.36]) with mapi id 14.03.0174.001; Tue, 4 Mar 2014 04:54:42 -0800 From: John Lilley To: "user@hadoop.apache.org" Subject: RE: decommissioning a node Thread-Topic: decommissioning a node Thread-Index: Ac83p5Uv9pmXPd6IRUKIP24kOBjJwwAATnMw Date: Tue, 4 Mar 2014 12:54:39 +0000 Message-ID: <869970D71E26D7498BDAC4E1CA92226B86E6DF54@MBX021-E3-NJ-2.exch021.domain.local> References: <869970D71E26D7498BDAC4E1CA92226B86E6DF0F@MBX021-E3-NJ-2.exch021.domain.local> In-Reply-To: <869970D71E26D7498BDAC4E1CA92226B86E6DF0F@MBX021-E3-NJ-2.exch021.domain.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.160.43.60] Content-Type: multipart/alternative; boundary="_000_869970D71E26D7498BDAC4E1CA92226B86E6DF54MBX021E3NJ2exch_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_869970D71E26D7498BDAC4E1CA92226B86E6DF54MBX021E3NJ2exch_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable OK, restarting all services now fsck shows under-replication. Was it the N= ameNode restart? John From: John Lilley [mailto:john.lilley@redpoint.net] Sent: Tuesday, March 04, 2014 5:47 AM To: user@hadoop.apache.org Subject: decommissioning a node Our cluster has a node that reboot randomly. So I've gone to Ambari, decom= missioned its HDFS service, stopped all services, and deleted the node from= the cluster. I expected and fsck to immediately show under-replicated blo= cks, but everything comes up fine. How do I tell the cluster that this nod= e is really gone, and it should start replicating the missing blocks? Thanks John --_000_869970D71E26D7498BDAC4E1CA92226B86E6DF54MBX021E3NJ2exch_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

OK, restarting all ser= vices now fsck shows under-replication. Was it the NameNode restart?<= o:p>

John=

From: John Lil= ley [mailto:john.lilley@redpoint.net]
Sent: Tuesday, March 04, 2014 5:47 AM
To: user@hadoop.apache.org
Subject: decommissioning a node

Our cluster has a node that reboot randomly. S= o I’ve gone to Ambari, decommissioned its HDFS service, stopped all s= ervices, and deleted the node from the cluster. I expected and fsck t= o immediately show under-replicated blocks, but everything comes up fine. How do I tell the cluster that this node is really go= ne, and it should start replicating the missing blocks?

Thanks

John

--_000_869970D71E26D7498BDAC4E1CA92226B86E6DF54MBX021E3NJ2exch_--