Mailing-List: contact common-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Mon, 21 Jun 2010 02:40:27 -0000
Message-ID: <20100621024027.10774.61848@eos.apache.org>
Subject: 
 =?utf-8?q?=5BHadoop_Wiki=5D_Trivial_Update_of_=22Hbase/MigrationToNewClus?=
 =?utf-8?q?ter=22_by_NatHarward?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for ch=
ange notification.

The "Hbase/MigrationToNewCluster" page has been changed by NatHarward.
The comment on this change is: Adding forgotten step to re-enable tables in=
 the new cluster if they were disabled in the original cluster.
http://wiki.apache.org/hadoop/Hbase/MigrationToNewCluster?action=3Ddiff&rev=
1=3D3&rev2=3D4

--------------------------------------------------

    i. I did a spot-check of file sizes and directories to my satisfaction =
-- depending on how important your data is you may want some kind of checks=
umming crawler for verification
    i. Run ''fsck'' to make sure HDFS is happy and does not think anything =
is wrong
   I. Fire up Hbase in the new cluster
-   i. Make sure your configuration points to the ''new'' Hbase root direct=
ory in the new cluster
+   i. Make sure your configuration points to the ''new'' Hbase root direct=
ory in the new cluster and your ''new'' Zookeeper instance
+   i. Enable all your tables if you disabled them originally
   I. Verify Hbase connectivity, and again to your satisfaction verify the =
data accessible through your new Hbase instance
   I. Finito!
 =20