Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of kwiley@keithwiley.com
 designates 69.93.179.18 as permitted sender)
From: Keith Wiley <kwiley@keithwiley.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Adding additional storage
Date: Mon, 27 Aug 2012 11:45:07 -0700
Message-Id: <5610A2D3-CE7D-4DB2-8D74-54903765D05F@keithwiley.com>
To: user@hadoop.apache.org
Mime-Version: 1.0 (Apple Message framework v1084)

I'm running a pseudo-distributed cluster on a single machine and I would =
like to use a larger disk (mounted and ready to go of course).  I don't =
mind transferring to the new disk (as opposed to using both disks for =
the hdfs which seems much hairier), but I'm not sure how to transfer a =
hadoop cluster to a new disk...or if its even possible.  Even if I =
simply copy the entire directory where the hdfs is emulated, I still =
need to somehow switch the namenode to know about the new disk?

Is there any way to do this that beats manually "getting" the data, =
throwing away the old cluster, making a new cluster from scratch, and =
reuploading the data to hdfs?...or is that really the only feasible way =
to migrate a pseudo-distributed cluster to a second larger storage?

Thanks.

=
__________________________________________________________________________=
______
Keith Wiley     kwiley@keithwiley.com     keithwiley.com    =
music.keithwiley.com

"You can scratch an itch, but you can't itch a scratch. Furthermore, an =
itch can
itch but a scratch can't scratch. Finally, a scratch can itch, but an =
itch can't
scratch. All together this implies: He scratched the itch from the =
scratch that
itched but would never itch the scratch from the itch that scratched."
                                           --  Keith Wiley
=
__________________________________________________________________________=
______