Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of amansk@gmail.com designates
 209.85.160.41 as permitted sender)
Date: Tue, 10 Jul 2012 21:42:52 -0700
From: Amandeep Khurana <amansk@gmail.com>
To: user@hbase.apache.org
Message-ID: <412A8071FF9B46E29054EC412D5BB879@gmail.com>
In-Reply-To: <CC2251B4.4EB%geliu@zynga.com>
References: <CC2251B4.4EB%geliu@zynga.com>
Subject: Re: Auto failover of HBase
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4ffd044c_75c6c33a_3553"

--4ffd044c_75c6c33a_3553
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Gen, 

HBase has HA across the entire stack. Have you read the original Google Bigtable paper to understand the architecture of the system? That is a great place to start.

-Amandeep 


On Tuesday, July 10, 2012 at 9:40 PM, Gen Liu wrote:

> Hi, I'm new here. I'm doing evaluation on Hbase before applying it to production with big traffic and data.
> I was search for detailed documents that specifying the auto failover behavior of Hbase, e.g. What happen if Master/RegionServer/Zookeeper die(maybe at the same time), how does administrators recover the cluster, is there any data lost if master is dead for a while, etc.
> 
> Any link, suggestion, help will be appreciated. Thanks.
> 
> Gen Liu 


--4ffd044c_75c6c33a_3553--