Return-Path: 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 0E5FDC98D for ; Tue, 11 Jun 2013 15:56:28 +0000 (UTC) Received: (qmail 60487 invoked by uid 500); 11 Jun 2013 15:56:23 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 60090 invoked by uid 500); 11 Jun 2013 15:56:22 -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 60082 invoked by uid 99); 11 Jun 2013 15:56:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 15:56:22 +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: local policy) Received: from [66.46.182.54] (HELO relay.ihostexchange.net) (66.46.182.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 15:56:16 +0000 Received: from VMBX103.ihostexchange.net ([192.168.3.3]) by HUB104.ihostexchange.net ([66.46.182.54]) with mapi; Tue, 11 Jun 2013 11:55:55 -0400 From: Michael Namaiandeh To: "user@hadoop.apache.org" Date: Tue, 11 Jun 2013 11:55:53 -0400 Subject: RE: Two Datanodes - Incompatible Cluster IDs Thread-Topic: Two Datanodes - Incompatible Cluster IDs Thread-Index: Ac5munCn2V7Kjv5GTWmt6H1WXWyXNwAAZw5Q Message-ID: References:

In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C83B1CD20DD48B4DB4AB87089B0117FA956FA7112FVMBX103ihoste_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_C83B1CD20DD48B4DB4AB87089B0117FA956FA7112FVMBX103ihoste_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Brilliant, Ian! That worked. Now, all my nodes are showing up as live. From: Ian Wrigley [mailto:ian@cloudera.com] Sent: Tuesday, June 11, 2013 11:43 AM To: user@hadoop.apache.org Subject: Re: Two Datanodes - Incompatible Cluster IDs If you just blow away the contents of the dfs.data.dir directories then sta= rt the DataNode daemon again you should be fine. (That's where the ClusterI= D is stored. When they next connect to the NameNode, because they don't hav= e one now that you've deleted it, they'll be given the one from the NameNod= e.) Regards Ian. On Jun 11, 2013, at 10:38 AM, Michael Namaiandeh > wrote: I am trying to setup a 4 node Cloudera Hadoop cluster. However; two of my d= ata nodes are showing up as "dead" nodes. After looking at the logs, I foun= d that the dead nodes have a different ClusterID than my working/"live" nod= es. How do I configure the dead nodes with the correct ClusterID. I can format= the dead nodes, if possible. Any help would be greatly appreciated. Thanks= . Mike --- Ian Wrigley Sr. Curriculum Manager Cloudera, Inc Cell: (323) 819 4075 --_000_C83B1CD20DD48B4DB4AB87089B0117FA956FA7112FVMBX103ihoste_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Brilliant, Ian! That worked. Now, all my nodes are showing up a= s live.

From: Ian Wrigley [mailto:ia= n@cloudera.com]
Sent: Tuesday, June 11, 2013 11:43 AM
To:<= /b> user@hadoop.apache.org
Subject: Re: Two Datanodes - Incompati= ble Cluster IDs

=

If you just blow away the contents of = the dfs.data.dir directories then start the DataNode daemon again you shoul= d be fine. (That's where the ClusterID is stored. When they next connect to= the NameNode, because they don't have one now that you've deleted it, they= 'll be given the one from the NameNode.)

Regards

Ian.

On Jun 11, 2013, at 10:38 AM, Michael= Namaiandeh <mnamaiandeh@he= althcit.com> wrote:

I am trying to setup a 4 nod= e Cloudera Hadoop cluster. However; two of my data nodes are showing up as = “dead” nodes. After looking at the logs, I found that the dead = nodes have a different ClusterID than my working/”live” nodes.<= span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>

How do I configure the dead nodes with the correct = ClusterID. I can format the dead nodes, if possible. Any help would b= e greatly appreciated. Thanks.

Mike

<= /div>

---
Ian Wrigley
Sr. Curriculum Manager
Cloudera, Inc
Cell= : (323) 819 4075

&nbs= p;

= --_000_C83B1CD20DD48B4DB4AB87089B0117FA956FA7112FVMBX103ihoste_--