[AMBARI-24615] Ambari - Manage Kafka Client Configs

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6.2
• Component/s: ambari-agent, ambari-client, ambari-server, ambari-web

Environment

HDP 2.6

• Assignee: Unassigned
• Reporter: Hari Sekhon
• Created: 10/Sep/18 15:13
• Updated: 10/Sep/18 15:15

Description

Request for Ambari to manage Kafka Client Configs.

Currently only brokers are listed so you cannot split Kafka client configs to another config group and deploy them to allow Kafka clients to use less memory. There is no way to deploy the Kafka client config updates in Ambari.

For example, if you have 8G heap allocated to Kafka brokers, clients fail to start on edge nodes as they cannot satisfy the broker's -Xms8G setting in kafka-env.sh, and splitting to a different config group for clients/brokers doesn't work as there is currently no way in Ambari to deploy the Kafka client config updates as only brokers are listed on summary page and there is no deploy client configurations type option, changes made to config only result in Restart Required for the few broker nodes.