Thanks Andrew for your comments. From the response seems like nobody has tried to do this ( starting/shutting-down ec2-clusters with the same EBS-backed-hdfs-hbase data ). It also seem to require some automated scripts to dynamically attach the EBS drives one to each slave.
Do we have anything from Cloudera folks in this regard yet ? -Prasen On Sun, Mar 14, 2010 at 2:47 AM, Andrew Purtell <apurt...@apache.org> wrote: > I thought about this some more and remembered we substitute the internal > DNS names allocated by EC2 into the config files, not IP addresses (and > that the EC2 internal DNS names embed what looks like a MAC address not an > IP address). So as long as the internal DNS name on an instance is stable > through suspension and resumption, the only pre-suspend and post-resume > steps necessary is graceful shutdown of the daemons and subsequent > relaunch, respectively. > > Graceful shutdown of the daemons prior to suspension will be necessary due > to how Hadoop and HBase services monitor their internal function and > trigger recovery actions. > > Maybe someone can experiment, confirm or refute, and then share their > experiences? > > - Andy > > > > ----- Original Message ---- >> From: Andrew Purtell <apurt...@apache.org> >> To: hbase-user@hadoop.apache.org >> Sent: Sat, March 13, 2010 12:32:22 PM >> Subject: Re: on Hadoop reliability wrt. EC2 (was: Re: [databasepro-48] HUG9) >> >> The data will be intact, but the config will be invalidated, right? > > > > >
