hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rong-En Fan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-546) Use Zookeeper in HBase
Date Thu, 22 Jan 2009 06:27:59 GMT

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

Rong-En Fan commented on HBASE-546:
-----------------------------------

For the sake of performance and reliability, HBase should start a small ZK cluster itself
(not necessary every HRS, but could be a list of nodes in conf/hbase-zk).

But I agree with what stack listed in Nov 11 above, esp, #5. We can start with a single-instance
ZK then change it if necessary. For example, if people mainly deal with HBase, they shouldn't
be bothered to get a ZK cluster up and running by themselves.


> 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: Critical
>             Fix For: 0.20.0
>
>         Attachments: DistributedLockInterface.java, hbase-546-scripts-v2.patch, hbase-546-scripts.patch,
HBASE-546-v2.patch, hbase-546-v3.patch, HBASE-546.patch, 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.


Mime
View raw message