[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082478#comment-16082478 ]
Ambud Sharma commented on AMBARI-21234: --------------------------------------- Added patch for trunk and branch-2.5 > Ambari rack awareness for Kafka > ------------------------------- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement > Components: ambari-server > Reporter: Ambud Sharma > Assignee: Sebastian Toader > Fix For: 2.5.2 > > Attachments: AMBARI-21234-2.5.diff, AMBARI-21234-trunk.diff > > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. > Design: > This stack change uses the /clusterHostInfo/all_hosts and > /clusterHostInfo/all_racks paths and materializes them to a variable. Then it > uses linear search to find this node in the list of all hosts and it's > corresponding rack id. This information is then stored in a variable called > rack and which is materialized during the configure method of the broker > scripts. > This stack change relies on the node rack information stored in Ambari > therefore will enable both Ambari UI and Blueprints to be used for setting up > Kafka broker rack information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)