hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Trivial Update of "ZooKeeper/HBaseUseCases" by stack
Date Fri, 20 Nov 2009 18:36:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "ZooKeeper/HBaseUseCases" page has been changed by stack.


  ZooKeeper recipes that HBase plans to use current and future. By documenting these cases
we (zk/hbase) can get a better idea of both how to implement the usecases in ZK, and also
ensure that ZK will support these. In some cases it may be prudent to verify the cases (esp
when scaling issues are identified). It may also be that new features, etc... might be identified.
  Currently, hbase clients find the cluster to connect to by asking zookeeper.  The only configuration
a client needs is the zk quorum to connect to.  Masters and hbase slave nodes (regionservers)
all register themselves with zk.  If their znode evaporates, the master or regionserver is
consided lost and repair begins.
+ HBase currently will default to manage the zookeeper cluster.   It does this in an attempt
at not burdening users with yet another technology to figure; things are bad enough for the
hbase noob what with hbase, hdfs, and mapreduce.  Part of hbase's management of zk includes
being able to see zk configuration in the hbase configuration files. Anything that has the
hbase.zookeeper prefix will have its suffix mapped to the corresponding zoo.cfg setting (HBase
parses its config. and feeds the relevant zk configurations to zk on start).
  Below is some more detail on current (hbase 0.20.x) hbase use of zk:

View raw message