ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Toader (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21234) Ambari rack awareness for Kafka
Date Wed, 21 Jun 2017 05:10:01 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebastian Toader updated AMBARI-21234:
--------------------------------------
    Component/s: ambari-server

> 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
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21234.patch
>
>
> 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)

Mime
View raw message