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 7D23BF142 for ; Thu, 18 Apr 2013 03:27:52 +0000 (UTC) Received: (qmail 62090 invoked by uid 500); 18 Apr 2013 03:27:47 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 61753 invoked by uid 500); 18 Apr 2013 03:27:46 -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 61715 invoked by uid 99); 18 Apr 2013 03:27:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 03:27:45 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 98.139.253.105 is neither permitted nor denied by domain of rajive@yahoo-inc.com) Received: from [98.139.253.105] (HELO mrout2-b.corp.bf1.yahoo.com) (98.139.253.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Apr 2013 03:27:41 +0000 Received: from GQ1-EX10-CAHT11.y.corp.yahoo.com (gq1-ex10-caht11.corp.gq1.yahoo.com [10.87.93.110]) by mrout2-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id r3I3R4nL082102 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 17 Apr 2013 20:27:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1366255625; bh=FQXRB7XtAVqMtue7V6kcFxsj8fXr1zr0NT72W93AO9U=; h=From:To:Subject:Date:Message-ID:In-Reply-To:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=KXnVpb1WBeR3OTDE9QtVwPy9dbOtbZ1J3HonsFyxNmS+Zicz3MK2hWAjVHFEZxMkp PakKH2e5J9HAp/pak4xRlsCS7lQAA6rr0rGhhWSkX0HJVyXRjT2BB0A0syBDU9OxHw L/J3IthcN5DV/HwmF9FxQUZo4sWZXl4gB4nOqog8= Received: from GQ1-MB03-02.y.corp.yahoo.com ([fe80::2cf1:821d:672a:c5cd]) by GQ1-EX10-CAHT11.y.corp.yahoo.com ([fe80::fced:19dc:eaca:7886%12]) with mapi id 14.02.0342.003; Wed, 17 Apr 2013 20:27:03 -0700 From: Rajiv Chittajallu To: "user@hadoop.apache.org" Subject: Re: Physically moving HDFS cluster to new Thread-Topic: Physically moving HDFS cluster to new Thread-Index: AQHOO5FG3LjFa3WSpE2C0M4FDbwuuJjbtY0A//+cfwA= Date: Thu, 18 Apr 2013 03:27:02 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.73.196.63] Content-Type: text/plain; charset="us-ascii" Content-ID: <8A104467A042A042A15DF4146A490B7D@yforest.corp.yahoo.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 255625001 X-Virus-Checked: Checked by ClamAV on apache.org On 4/17/13 7:23 PM, "Ted Dunning" wrote: > >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. This is not correct. In HDFS, As long as the fsimage and copy of a data block are kept intact you can do any changes to the nodes. > >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 > > > > > >