Hari Sekhon created AMBARI-24615: ------------------------------------ Summary: Ambari - Manage Kafka Client Configs Key: AMBARI-24615 URL: https://issues.apache.org/jira/browse/AMBARI-24615 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-client, ambari-server, ambari-web Affects Versions: 2.6.2 Environment: HDP 2.6 Reporter: Hari Sekhon
Ambari doesn't manage Kafka Client Configs(only brokers are listed) so you cannot split Kafka client configs to allow Kafka clients to use less memory and then deploy the client config updates. 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, and there is no way to split the configs as you cannot deploy the client config updates as only brokers are listed on summary page and there is no deploy client configurations type option, changes made only result in Restart Required for the few broker nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)