hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: Are there any single points of failure in a HBase configuration
Date Tue, 16 Jun 2009 21:04:58 GMT
HBase itself doesn't strictly have any SPOF in 0.20.  Multiple master
failover, etc.

HBase depends on HDFS, which does have a SPOF in it's namenode.  If that
goes down, everything is down.  Generally speaking, namenode is reliable,
but the hardware is the issue.  You can have a quick recovery, but still

HBase isn't explicitly designed to run across a WAN split between 2
datacenters.  It's certainly possible, but during certain link-down
scenarios you are looking at cluster splits.  HBase master will decide those
regionservers no longer reachable have died, and HDFS will assume those
datanodes lost are gone, and start to replicate data.

In HBase 0.21, we are hoping to have replication support between clusters.


On Tue, Jun 16, 2009 at 1:53 PM, Fred Zappert <fzappert@gmail.com> wrote:

> Hi,
> We're considering HBase for a customer-facing SaaS.  I saw some references
> to Master instance, and failure/failover scenarios on this list.
> We would be running this across at least two data centers in different
> cities or sates.
> Which leads to the following questions:
> 1. Are there any single points of failure in an HBase configuration.
> 2: What would be the impact of one data center being down?
> 3: What would be the recovery time and procedure to restore normal
> operation
> on a new master?
> There are approximately 4M transactions/day
> Thanks,
> Fred.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message