Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 99139 invoked from network); 10 Aug 2010 18:02:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Aug 2010 18:02:18 -0000 Received: (qmail 1474 invoked by uid 500); 10 Aug 2010 18:02:15 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 1280 invoked by uid 500); 10 Aug 2010 18:02:15 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 1272 invoked by uid 99); 10 Aug 2010 18:02:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 18:02:15 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of awittenauer@linkedin.com designates 69.28.149.25 as permitted sender) Received: from [69.28.149.25] (HELO esv4-mav03.corp.linkedin.com) (69.28.149.25) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 18:02:08 +0000 DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns; h=X-IronPort-AV:Received:From:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version; b=JLsw6n7D52WtNr/uEGtKKPkqzxBKdTFCucE73F6j0qUGkpLIIM8/SZVd MCmC+3FTwXhZ4cQhq1+AXE/1mZIxgegLnUI5EaGloUIud5hKUTxz9ctKz BoYgO14ZdLaLMV+; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=linkedin.com; i=awittenauer@linkedin.com; q=dns/txt; s=proddkim; t=1281463328; x=1312999328; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Allen=20Wittenauer=20 |Subject:=20Re:=20Changing=20hostnames=20of=20tasktracker /datanode=20nodes=20-=20any=20problems?|Date:=20Tue,=2010 =20Aug=202010=2018:01:47=20+0000|Message-ID:=20|To:=20""=20,=0D=0A=09""=20|MIME-Version:=201.0|Content-Transfer-Encoding:=20quot ed-printable|Content-ID:=20<24d0371f-940b-425d-b2c3-bc479 b672735>|In-Reply-To:=20|References:=20<2010081012 5148.21de61b6@caputradii.linkoping.osa>=0D=0A=20=0D=0A=20<26815 447-E92A-419D-84B7-C5448701F7B8@cse.unl.edu>=0D=0A=20=0D=0A=20< AANLkTimzRPHQqu5hzWoiKQZOkC8=3DGJ-7+U_2BsWBsh4w@mail.gmai l.com>; bh=xb5d9ux+ZVpgy25Zu8/VhjUKXwqk9poLxJ0SpRQxW1c=; b=uVuCsvJiU9yhoNWcxcl5fwnGlSFx7HYwMqfrejdnvFJNnh+OtPvqFNp1 WzPh/20CO7C1RcKDoQHqlWKkqcNfivdYioo1VsvcvcMcKrQAzG+ZhAaXJ EbcK1pDjHvnoj5P; X-IronPort-AV: E=Sophos;i="4.55,349,1278313200"; d="scan'208";a="14153937" Received: from ESV4-EXC01.linkedin.biz ([fe80::d7c:dc04:aea1:97d7]) by esv4-cas01.linkedin.biz ([172.18.46.140]) with mapi; Tue, 10 Aug 2010 11:01:47 -0700 From: Allen Wittenauer To: "" , "" Subject: Re: Changing hostnames of tasktracker/datanode nodes - any problems? Thread-Topic: Changing hostnames of tasktracker/datanode nodes - any problems? Thread-Index: AQHLOHoe8470P0Hb+EazRuRtbUcClpLbKCuAgAAG8ICAAB87gIAAIDEAgAACEIA= Date: Tue, 10 Aug 2010 18:01:47 +0000 Message-ID: References: <20100810125148.21de61b6@caputradii.linkoping.osa> <26815447-E92A-419D-84B7-C5448701F7B8@cse.unl.edu> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-ID: <24d0371f-940b-425d-b2c3-bc479b672735> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org On Aug 10, 2010, at 10:54 AM, Bill Graham wrote: > Is is correct to say that that would work fine? We have a replication fac= tor > of 2, so we'd be copying twice as much data as we'd need to so I'm sure > there's a more efficient approach. It should work fine. But yes, highly inefficient. > What about adding the new nodes in the new colo to the existing cluster, > rebalancing and then decommissioning the old cluster nodes before finally > migrating the NN/SNN? I know Hadoop isn't intended to run cross-colo, but > would this be a more efficient approach than the one above? If you can keep both grids up at the same time, use distcp to do the copy. = This will make sure the blocks get copied once, will keep permissions with= -p, keep the replication factor, redistribute data (free balancing!), etc,= etc, etc.