[KUDU-2574] add unique Cluster ID to Kudu cluster instances

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.1
• Fix Version/s: 1.14.0
• Component/s: client, master
• Labels: backup roadmap-candidate
• Assignee: Grant Henke
• Reporter: Dan Burkert
• Created: 07/Sep/18 22:39
• Updated: 21/Sep/20 15:34
• Resolved: 03/Sep/20 19:52

Description

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.

Issue Links

• is related to: KUDU-65 TS should refuse to re-register to different cluster
• relates to: KUDU-3196 Include and optionally validate cluster ID in backup and restore jobs
• relates to: KUDU-3192 Leverage cluster ID when playing HMS notifications