Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4E06FA1A for ; Sat, 23 Mar 2013 02:14:53 +0000 (UTC) Received: (qmail 4965 invoked by uid 500); 23 Mar 2013 02:14:48 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 4852 invoked by uid 500); 23 Mar 2013 02:14:48 -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 4844 invoked by uid 99); 23 Mar 2013 02:14:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Mar 2013 02:14:48 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Mar 2013 02:14:44 +0000 Received: by mail-oa0-f41.google.com with SMTP id f4so2460556oah.14 for ; Fri, 22 Mar 2013 19:14:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:x-originating-ip:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:x-gm-message-state; bh=wvSw2G3C1fNDyL5G8T8pavoIfAag77BKv8LWgczED1A=; b=DHBadBRXsirDJJM9Zi0f0yMxd1/31S0ShgbEC/e65J3grtFE93cnUPj9SKRhoZx4Gx nrCvHOVEd1YAIkN3SqjIVtip7sGkFDoD+jxju/kxzqX7qTXFJjO/P0FPo75nK8IskmZg te7OK6NxN7chjG/EWmLMfTLe+2sOLydG/nG/bckKhNFtMub0k0LG8Txi9ua865SZOWVX zW6ZHHjD8VlzRZqRk2OODvKAG/ABmjHlUWmN5AWcHO9G/NETQ7vqiYAeksm2819QniSb OZdhml33SKXSnqJDNgyButIhpv6nOaeUBj/CMj+CHSnZThZMD1IKpv55f672yyRay2T2 Fdfw== MIME-Version: 1.0 X-Received: by 10.60.10.138 with SMTP id i10mr4044322oeb.95.1364004861102; Fri, 22 Mar 2013 19:14:21 -0700 (PDT) Sender: balaji@balajin.net Received: by 10.76.83.74 with HTTP; Fri, 22 Mar 2013 19:14:20 -0700 (PDT) X-Originating-IP: [107.3.139.194] In-Reply-To: References: Date: Fri, 22 Mar 2013 19:14:20 -0700 X-Google-Sender-Auth: uvzJygdZ30loDM8TlKgYZMKVIfc Message-ID: Subject: Re: Cluster lost IP addresses From: =?UTF-8?B?QmFsYWppIE5hcmF5YW5hbiAo4K6q4K6+4K6y4K6+4K6c4K6/IOCuqOCuvuCusOCuvuCur+Cuow==?= =?UTF-8?B?4K6p4K+NKQ==?= To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=e89a8f5036fc37e83f04d88e212d X-Gm-Message-State: ALoCoQn6Q02KDEbQEWOX5YYCJtLsLfUPcf8s9r5q+qAEZeNBSO3D+g0k/F1ToIpmWYBqGZU++UXl X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f5036fc37e83f04d88e212d Content-Type: text/plain; charset=UTF-8 Assuming you are using hostnAmes and not ip address in your config files What happens when you start the cluster? If you are using IP address in your configs just update them and start. It should work with no issues. On Friday, March 22, 2013, John Meza wrote: > I have a 18 node cluster that had to be physically moved. > Unfortunately all the ip addresses were lost (recreated). > > This must have happened to someone before. > Nothing else on the machines has been changed. Most importantly the data > in HDFS is still sitting there. > > Is there a way to recover this cluster to a useable state? > thanks > John > -- http://balajin.net/blog http://flic.kr/balajijegan --e89a8f5036fc37e83f04d88e212d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Assuming you are using hostnAmes and not ip address in your config files=C2= =A0What happens when you start the cluster? If you are using IP address in = your configs just update them and start. It should work with no issues. =C2= =A0

On Friday, March 22, 2013, John Meza wrote:
I have a 18 node cluster that had to be physically mo= ved.
Unfortunately all the ip addresses were lost (recreated).

This must have happened to someone before.
Nothi= ng else on the machines has been changed. Most importantly the data in HDFS= is still sitting there.

Is there a way to recover this cluster to a useable sta= te?
thanks
John


--
http://bala= jin.net/blog
http://flic.kr/b= alajijegan
--e89a8f5036fc37e83f04d88e212d--