Funky, cause HBase is often presented as a 3-layers server model
zookeeper/master/region (root/meta in the regions bringing still more fogs).
Maybe the commonly understanding in the community is that HBase's
HMaster is like Hadoop's NameNode, which is not the case (NameNode's
failure will bring your cluster down, HMaster's failure will not...).
Upon presentation simplification (via 'master' renaming, or at least via
explanation emphases), having a more simple model such as the one
described in HBASE-3171 could help (this is my very short opinion, I
remember having read valid arguments against that model).
client<->zk<->(master)<->region(root|master)
or
client<->zk<->region (+admin)
the latter looks simpler, doesn't it?
Thx,
Eric
On 11/02/12 16:45, Stack wrote:
2012/2/11 Eric Charles<[email protected]>:
Hypothetical case (probably asked a number of time here, sorry...):
Can a client correcty put, get, scan (no admins tasks such as create
table,...) with a HBase cluster having its HMaster process down ?
It can Eric. Kill your master and you can do all the above.
St.Ack
--
eric | http://about.echarles.net | @echarles
