[
https://issues.apache.org/jira/browse/KUDU-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2574:
------------------------------
Labels: backup (was: )
> 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
>
> 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
(v7.6.3#76005)
