Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 2F417FFA6 for ; Thu, 18 Apr 2013 02:24:24 +0000 (UTC) Received: (qmail 89880 invoked by uid 500); 18 Apr 2013 02:24:19 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 89803 invoked by uid 500); 18 Apr 2013 02:24:19 -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 89794 invoked by uid 99); 18 Apr 2013 02:24:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 02:24:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.217.172] (HELO mail-lb0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 02:24:12 +0000 Received: by mail-lb0-f172.google.com with SMTP id u10so2244741lbi.17 for ; Wed, 17 Apr 2013 19:23:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=Z5NceIBtDILBYzX1fc+yaqKxau/Kx902/yXJDipsuFM=; b=ogbkSKG8/YwCLS9UuDFyRzhFFo+7NJqCuhJGPfPtz0gxHmCS7MSJEiM+w8065sNBcp kOSQ7aI2k4yP2yXeldK+wUOw5bGAZyP/L1D0972QsJEn8wqSprHo/rm7S+pFUqEjyN+E CJlOZN2SP7GcRGbT10n//kt6WD4fqzuPHWuSeY7yqs0jf9DweGc2LabXIddkQmDlQ+KI i1RAK90GC8FYX4BCY4b6kg34CBF4Z9G2fs3a3VvLHExoioo5fc14WyIC4IFkCuHG1Yfg VHdfWdFuzmE+mGydzuqOEyYVyW4bpn6ukcycEiDvhw3hjBgwCn2EkJjvBPS7vy1cbygD URmA== X-Received: by 10.112.145.132 with SMTP id su4mr4664133lbb.76.1366251810897; Wed, 17 Apr 2013 19:23:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.8.33 with HTTP; Wed, 17 Apr 2013 19:23:10 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Thu, 18 Apr 2013 02:23:10 +0000 Message-ID: Subject: Re: Physically moving HDFS cluster to new To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7b3a81fedcd39004da994998 X-Gm-Message-State: ALoCoQkWDdfTEmpKtX2Lj6JPwqZ/MeDbfS0nfBsog6ooke/O7gHbHkE/7GOsVf3mKBhDk8G6mZE3 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3a81fedcd39004da994998 Content-Type: text/plain; charset=ISO-8859-1 It may or may not help you in your current distress, but MapR's distribution could handle this pretty easily. One method is direct distcp between clusters, but you could also use MapR's mirroring capabilities to migrate data. You can also carry a MapR cluster, change the IP addresses and relight the cluster without data loss. You can also move disks (respecting RAID-0 disk groups, of course) from machine to machine within a cluster and have them wake up with all file and directory meta-data intact. Furthermore, you can lose any two machines in a cluster and are guaranteed to be able to reconstruct the cluster. Even if you lose all three replicas of *any* of the data or meta-data in the cluster, you can *still* reconstruct any data volumes for which at least one copy survives. The the lost data volumes come back at a later time, you will also be able resurrect the data correctly. None of this is true for any of the other major Hadoop distributions. Let me know if you want to try this out. On Wed, Apr 17, 2013 at 5:20 PM, Tom Brown wrote: > We have a situation where we want to physically move our small (4 node) > cluster from one data center to another. As part of this move, each node > will receive both a new FQN and a new IP address. As I understand it, HDFS > is somehow tied to the the FQN or IP address, and changing them causes data > loss. > > Is there any supported method of moving a cluster this way? > > Thanks in advance! > > --Tom > --047d7b3a81fedcd39004da994998 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

It may or may not help you in your current = distress, but MapR's distribution could handle this pretty easily.

One method is direct distcp between cluste= rs, but you could also use MapR's mirroring capabilities to migrate dat= a.

You can also carry a MapR cluster, change t= he IP addresses and relight the cluster without data loss. =A0You can also = move disks (respecting RAID-0 disk groups, of course) from machine to machi= ne within a cluster and have them wake up with all file and directory meta-= data intact.

Furthermore, you can lose any two machines = in a cluster and are guaranteed to be able to reconstruct the cluster. =A0E= ven if you lose all three replicas of *any* of the data or meta-data in the= cluster, you can *still* reconstruct any data volumes for which at least o= ne copy survives. =A0The the lost data volumes come back at a later time, y= ou will also be able resurrect the data correctly.

None of this is true for any of the other m= ajor Hadoop distributions.

Let me know= if you want to try this out.





On Wed, Apr 17, 2013 at 5:20 PM, Tom Brown <tombrow= n52@gmail.com> wrote:
We have a situation where w= e want to physically move our small (4 node) cluster from one data center t= o another. As part of this move, each node will receive both a new FQN and = a new IP address. As I understand it, HDFS is somehow tied to the the FQN o= r IP address, and changing them causes data loss.

Is there any supported method of moving a cluster this = way?

Thanks in advance!

--Tom

--047d7b3a81fedcd39004da994998--