You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/09/10 15:16:00 UTC
[jira] [Updated] (AMBARI-24615) Ambari - Manage Kafka Client
Configs
[ https://issues.apache.org/jira/browse/AMBARI-24615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Sekhon updated AMBARI-24615:
---------------------------------
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.
was:
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.
> 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
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)