[
https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Helmling updated HBASE-3677:
---------------------------------
Attachment: HBASE-3677_final.patch
Final patch committed to trunk (#3 from review).
> Generate a globally unique identifier for a cluster and store in
> /hbase/hbase.id
> --------------------------------------------------------------------------------
>
> Key: HBASE-3677
> URL: https://issues.apache.org/jira/browse/HBASE-3677
> Project: HBase
> Issue Type: Improvement
> Components: master
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Fix For: 0.92.0
>
> Attachments: HBASE-3677_final.patch
>
>
> We don't currently have a way to uniquely identify an HBase cluster, apart
> for where it's stored in HDFS or configuration of the ZooKeeper quorum
> managing it. It would be generally useful to be able to identify a cluster
> via API.
> The proposal here is pretty simple:
> # When master initializes the filesystem, generate a globally unique ID and
> store in /hbase/hbase.id
> # For existing clusters, generate hbase.id on master startup if it does not
> exist
> # Include unique ID in ClusterStatus returned from master
> For token authentication, this will be required to allow selecting the
> correct token to pass to a cluster when a single client is communicating to
> more than one HBase instance.
> Chatting with J-D, replication stores it's own cluster id in place with each
> HLog edit, so requires as small as possible an identifier, but I think we
> could automate a mapping from unique cluster ID -> short ID if we had the
> unique ID available.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
