Provides a cluster id setting that can be accessed programmatically

Description

In order to support multi-clusters setup, user programs need to have something to identify which cluster it is running, in order to determine what configurations to use. The CDAP platform can further provide runtime arguments scoped resolution based on the cluster id as well.

Release Notes

Adds cluster.name property that identifies a cluster, this property can be set in cdap-site.xml

Activity

Show:
Terence Yim
December 12, 2016, 2:20 AM
Ali Anwar
December 14, 2016, 9:36 PM

"The CDAP platform can further provide runtime arguments scoped resolution based on the cluster id as well."
How is that different than preferences that are set at the instance level?

Terence Yim
December 17, 2016, 1:24 AM
Edited

This is for the replication case. Preferences are replicated, meaning two clusters have exactly the same preferences. With cluster id, one can set it to different value in `cdap-site.xml` for different cluster, and have keys like `cluster.cluster1.kafka.brokers` and `cluster.cluster2.kafka.brokers` in preferences. At program runtime, the program just need to get `kafka.brokers` and it will be resolved to either `cluster.cluster1.kafka.brokers` or `cluster.cluster2.kafka.brokers` based on which cluster that the program is currently running.

Fixed

Assignee

Terence Yim

Reporter

Terence Yim

Labels

Docs Impact

None

UX Impact

None

Components

Fix versions

Priority

Major
Configure