[
https://issues.apache.org/jira/browse/HBASE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604536#action_12604536
]
Jean-Daniel Cryans commented on HBASE-546:
------------------------------------------
In Bigtable paper, page 4, it describes what Chubby is used for exactly :
- Ensure there is at most 1 active master at any time
- Store the bootstrap location
- Discover tablet servers and finalize tabler server death
- Store the schema information
- Store access control lists (not sure what it is)
Ze big question : do we want to implement all of these or just some parts? For
example, what would be the benefit of storing all schema information in ZK
instead of what we do right now?
> 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
> Attachments: 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.
