[ 
https://issues.apache.org/jira/browse/HBASE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604036#action_12604036
 ] 

stack commented on HBASE-546:
-----------------------------

(after chatting w/ J-D on IRC), I wonder if we should just treat ZK as we 
currently treat HDFS -- its just an address in the hbase-*.xml?  Something like:

{code}
<property>
<name>hbase.zookeeper</name>
</name>
<value>ZK_HOST:ZK_PORT/ZK_DATADIR
</value>
</property>
{code}

Would be grand if no zookeeper configured, we fell back on hbase-only 
implementation of ZK interface (Would we need to have master and regionservers 
listening on two ports to do this?)

Would mean user would have to configure the ZK cluster independent of hbase.  
Would have to also do the clean independently of hbase too, just as you do hdfs 
currently.

Alternatively, we'd have a zookeepers file which would have zookeeper 
configurations and a list of ZK cluster members with demarcation of leader.  On 
startup, we'd parse ZK settings and write out a ZK configuration on all ZK 
members of ZK cluster -- probably in shell --   and start up all members as 
part of bringing up ZK cluster.  Downside to latter is that it would take a bit 
more work and what to do if ZK cluster is for more than just hbase usage?  
Upside, user wouldn't have to worry about ZK.

> Use Zookeeper in HBase
> ----------------------
>
>                 Key: HBASE-546
>                 URL: https://issues.apache.org/jira/browse/HBASE-546
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Bryan Duxbury
>            Priority: Trivial
>
> Zookeeper =~ Chubby. This means that we could take advantage of a distributed 
> lock manager to coordinate things like failover masters, regionservers 
> staying online when master is dead, atomic region->regionserver assignments, 
> etc. There are a lot of opportunities for improvements here. Please add 
> discussions of particular features in comments or sub-tasks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to