Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of bradyzhong2018@gmail.com
 designates 74.125.82.174 as permitted sender)
MIME-Version: 1.0
Date: Mon, 8 Apr 2013 22:39:20 +0800
Message-ID: 
 <CAHk34rmc0ZTqx1w=+6RmPyh=4b9J+CmQzHNVR=am1=K5Y_qsog@mail.gmail.com>
Subject: About distributed lock service in HBase
From: Brady Zhong <bradyzhong2018@gmail.com>
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b5d34e8fbed9b04d9da66ee

--047d7b5d34e8fbed9b04d9da66ee
Content-Type: text/plain; charset=UTF-8

Hi all,

My name is Brady Zhong, a college student using HBase to develop our own
project. Currently I confronted with a problem. Since we need some kind of
high availability, we hope HBase can keep available even though the HMaster
goes down. Here're my questions:

1. Can HBase work during the node failure of HMaster? Can users write or
read the database before the switch and recovery of HMaster?
2. Why not use Zookeeper as distributed lock service for HBase, like Chubby
for Google Big Table?

Thanks very much for any help in advance.


Best regards,
Brady Zhong

--047d7b5d34e8fbed9b04d9da66ee--