You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2011/03/21 19:47:06 UTC
[jira] [Created] (HBASE-3677) Generate a globally unique identifier
for a cluster and store in /hbase/hbase.id
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
Priority: Minor
Fix For: 0.92.0
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
[jira] [Commented] (HBASE-3677) Generate a globally unique
identifier for a cluster and store in /hbase/hbase.id
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012219#comment-13012219 ]
Gary Helmling commented on HBASE-3677:
--------------------------------------
Posted patch for review here: http://review.cloudera.org/r/1669/
> 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
>
>
> 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
[jira] [Updated] (HBASE-3677) Generate a globally unique identifier
for a cluster and store in /hbase/hbase.id
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-3677) Generate a globally unique
identifier for a cluster and store in /hbase/hbase.id
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014744#comment-13014744 ]
stack commented on HBASE-3677:
------------------------------
Posted review over on rb G.
> 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
>
>
> 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
[jira] [Updated] (HBASE-3677) Generate a globally unique identifier
for a cluster and store in /hbase/hbase.id
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-3677:
----------------------------------
Priority: Major (was: Minor)
Raising priority. HBase MR token auth against multiple clusters will be hard to do without it.
> 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
> Fix For: 0.92.0
>
>
> 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
[jira] [Assigned] (HBASE-3677) Generate a globally unique
identifier for a cluster and store in /hbase/hbase.id
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling reassigned HBASE-3677:
------------------------------------
Assignee: Gary Helmling
> 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
>
>
> 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
[jira] [Commented] (HBASE-3677) Generate a globally unique
identifier for a cluster and store in /hbase/hbase.id
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016298#comment-13016298 ]
Hudson commented on HBASE-3677:
-------------------------------
Integrated in HBase-TRUNK #1832 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1832/])
HBASE-3677 Generate a globally unique cluster ID
> 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
[jira] [Resolved] (HBASE-3677) Generate a globally unique
identifier for a cluster and store in /hbase/hbase.id
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling resolved HBASE-3677.
----------------------------------
Resolution: Fixed
Release Note: Added a unique cluster ID to ClusterStatus, This makes the HMasterInterface RPC protocol incompatible with previous versions.
Hadoop Flags: [Incompatible change, Reviewed]
Committed to trunk.
> 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