You can do a variety of things, including having the namenode run on an incredibly resilient piece of hardware, (raid 1, redundant psus, etc).
>From the software perspective, you can look at the avatar node: http://hadoopblog.blogspot.com/2010/02/hadoop-namenode-high-availability.html or something like this: http://www.cloudera.com/blog/2009/07/hadoop-ha-configuration/ On Sat, Oct 29, 2011 at 11:46 AM, Mark <[email protected]> wrote: > How does one deal with the fact that HBase has a single point of failure.. > namely the namenode. What steps can be taken to eliminate and/or minimize > the impact of a namenode failure? What can a situation where reliability is > of utmost importance should one choose an alternative technology.. ie > Cassandra? > > Thanks >
