[ https://issues.apache.org/jira/browse/AMBARI-14887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Beerbower updated AMBARI-14887: ----------------------------------- Status: Patch Available (was: In Progress) > Atlas Integration : Fix Atlas-Kafka properties for Blueprints > ------------------------------------------------------------- > > Key: AMBARI-14887 > URL: https://issues.apache.org/jira/browse/AMBARI-14887 > Project: Ambari > Issue Type: Bug > Reporter: Tom Beerbower > Assignee: Tom Beerbower > Attachments: AMBARI-14887.patch > > > 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")); -- This message was sent by Atlassian JIRA (v6.3.4#6332)