[ 
https://issues.apache.org/jira/browse/KUDU-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190378#comment-17190378
 ] 

ASF subversion and git services commented on KUDU-2574:
-------------------------------------------------------

Commit 6689ba3c81be193309afd27de016dd35c0db71de in kudu's branch 
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=6689ba3 ]

KUDU-2574: Add a unique cluster ID

This patch adds a unique cluster ID to the cluster. The ID is
a UUID that is automatically generated and stored in the
sys_catalog if missing (on fresh startup or upgrade).

This patch also exposes the cluster ID via the masters web-ui
and the `kudu master list` tool.

I plan to use this cluster ID to enhance the HMS sync
functionality, but it can be exposed further as
needed for other uses as well.

Change-Id: I4df1d3f7d100336f52563f3008cacf6d9e328fae
Reviewed-on: http://gerrit.cloudera.org:8080/16403
Reviewed-by: Alexey Serbin <[email protected]>
Reviewed-by: Andrew Wong <[email protected]>
Tested-by: Kudu Jenkins


> add unique Cluster ID to Kudu cluster instances
> -----------------------------------------------
>
>                 Key: KUDU-2574
>                 URL: https://issues.apache.org/jira/browse/KUDU-2574
>             Project: Kudu
>          Issue Type: Improvement
>          Components: client, master
>    Affects Versions: 1.7.1
>            Reporter: Dan Burkert
>            Priority: Major
>              Labels: backup, roadmap-candidate
>
> The Kudu/HMS integration currently assumes that any Kudu table entry in the 
> HMS (as identified by the Kudu storage handler) belongs to the Kudu cluster 
> instance.  It seems increasingly likely that we will need to support 
> deployments where a single HMS is shared among multiple Kudu cluster 
> instances.  In order to disambiguate the HMS entries, we could introduce a 
> unique per-cluster ID and add it to the HMS entries.  The cluster ID would be 
> written durably to the master's sys catalog during startup.  Eventually we 
> would want tools and client APIs to inspect the cluster ID.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to