-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60249/
-----------------------------------------------------------
(Updated July 13, 2017, 5:14 p.m.)
Review request for Ambari, Alejandro Fernandez and Sriharsha Chintalapani.
Bugs: AMBARI-21234
https://issues.apache.org/jira/browse/AMBARI-21234
Repository: ambari
Description
-------
Ambari rack awareness for Kafka.
https://issues.apache.org/jira/browse/AMBARI-21234
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.
Diffs (updated)
-----
ambari-server/src/main/resources/common-services/KAFKA/0.10.0/configuration/ranger-kafka-audit.xml
PRE-CREATION
ambari-server/src/main/resources/common-services/KAFKA/0.10.0/kerberos.json
PRE-CREATION
ambari-server/src/main/resources/common-services/KAFKA/0.10.0/metainfo.xml
PRE-CREATION
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/kafka.py
1327090aa7
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
c36a10ff28
ambari-server/src/main/resources/stacks/HDP/2.5/services/KAFKA/metainfo.xml
12f6c45396
Diff: https://reviews.apache.org/r/60249/diff/8/
Changes: https://reviews.apache.org/r/60249/diff/7-8/
Testing
-------
Manually deployed Kafka cluster and verified the broker.rack property is
correctly populated.
File Attachments
----------------
trunk patch
https://reviews.apache.org/media/uploaded/files/2017/07/11/b3e15e0d-a677-49bb-a3c9-6287181d60c3__AMBARI-21234-trunk.diff
Thanks,
Ambud Sharma
