[AMBARI-14887] Atlas Integration : Fix Atlas-Kafka properties for Blueprints

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Tom Beerbower
• Reporter: Tom Beerbower
• Created: 02/Feb/16 21:21
• Updated: 20/Oct/16 19:43
• Resolved: 20/Oct/16 19:43

Description

The mechanism of setting the topology related properties(kafka and zk) in the agent will result in issues with blueprint installs.

Because each node in a blueprint provisioned cluster is provisioned independently of other nodes, the blueprint topology manager needs to block provisioning of all nodes until all hosts required for configuration topology resolution are known. This is determined in BlueprintConfigurationProcessor. Because these configurations are not registered with the blueprint configuration processor it is possible for the atlas host to be provisioned prior to the Kafka hosts being known which result in the failure of the agent to set these topology related properties.

In BlueprintConfigurationProcessor you will need too register updaters for all of the topology related properties, in this case "atlas.kafka.bootstrap.servers" and "atlas.kafka.zookeeper.connect".

For example:
atlasPropsMap.put("atlas.kafka.bootstrap.servers", new MultipleHostTopologyUpdater("KAFKA_BROKER"));

Issue Links

• duplicates: AMBARI-17031 Atlas Integration : Deploying HA Blueprint with Atlas does not work
• relates to: AMBARI-14853 Atlas Integration: Support deploying latest Atlas(which depends on kafka) using Ambari
• links to: code review and patch