[ https://issues.apache.org/jira/browse/KAFKA-14098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Egerton updated KAFKA-14098: ---------------------------------- Priority: Minor (was: Major) > Internal Kafka clients used by Kafka Connect should have distinguishable > client IDs > ----------------------------------------------------------------------------------- > > Key: KAFKA-14098 > URL: https://issues.apache.org/jira/browse/KAFKA-14098 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect > Reporter: Chris Egerton > Assignee: Chris Egerton > Priority: Minor > > KAFKA-5061 dealt with the lack of automatically-provided client IDs for the > Kafka clients used for source and sink tasks, and has been addressed for some > time now. Additionally, when new features have required new Kafka clients to > be brought up for tasks (such as the need for an admin client to create > topics for source tasks introduced by > [KIP-158|https://cwiki.apache.org/confluence/display/KAFKA/KIP-158%3A+Kafka+Connect+should+allow+source+connectors+to+set+topic-specific+settings+for+new+topics]), > we have taken care to ensure that these clients are also given meaningful > client IDs. > However, the internal clients used by Kafka Connect workers to create, > consume from, and produce to internal topics do not have > automatically-provided client IDs at the moment, and it is up to users to > manually supply them. Worse yet, even if a user does manually supply a client > ID for their Connect cluster's internal clients (by setting the {{client.id}} > property in their worker configuration), there is no distinction made between > the clients created for interacting with different topics. > If no {{client.id}} property is set in the worker config, Kafka Connect > should automatically provide client IDs for its internal clients that > includes the group ID of the cluster (if running in distributed mode) and the > purpose of the client (such as {{{}statuses{}}}, {{{}configs{}}}, or > {{{}offsets{}}}). -- This message was sent by Atlassian Jira (v8.20.10#820010)