You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/11/11 20:21:44 UTC

[jira] Commented: (HBASE-546) Use Zookeeper in HBase

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

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

Bunch of us had chat on ZK integration for 0.20.0 up on IRC.  Below was result:

{code}
19:01 < st^Ack_> So, let me try summarize.
19:01 < st^Ack_> 1. Zk all the time
19:01 < st^Ack_> 2. We manage a single instance as default
19:01 < st^Ack_> 3. Unless, user supplies URL to a ZK cluster, then we stop starting/stopping zk instance as part of cluster start/stop
19:02 < st^Ack_> 4. Look at having our single instance log to hdfs, can be done later
...
19:11 < jdcryans> 5. Look at managing a bigger ZK cluster later
{code}

> 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
>            Assignee: Jean-Daniel Cryans
>            Priority: Trivial
>             Fix For: 0.20.0
>
>         Attachments: DistributedLockInterface.java, zookeeper-config.patch
>
>
> 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.