You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Chris Egerton (Jira)" <ji...@apache.org> on 2023/03/31 14:51:00 UTC

[jira] [Resolved] (KAFKA-14838) MM2 Worker/Connector/Task clients should specify client ID based on flow and role

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

Chris Egerton resolved KAFKA-14838.
-----------------------------------
    Resolution: Done

> MM2 Worker/Connector/Task clients should specify client ID based on flow and role
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-14838
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14838
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Daniel Urban
>            Assignee: Daniel Urban
>            Priority: Major
>             Fix For: 3.5.0
>
>
> MM2 code creates a lot of Kafka clients internally. These clients generate a lot of logs, but since the client.id is not properly specified, connecting the dots between a specific Connector/Task and its internal client is close to impossible. This is even more complex when MM2 is running in distributed mode, in which multiple Connect workers are running inside the same process.
> For Connector/Task created clients, the client.id  clients should specify the flow, the Connector name/Task ID and the role of the client. E.g. MirrorSourceConnector uses multiple admin clients, and their client.id should reflect the difference between them.
> For Worker created clients, the client.id should refer to the flow.
> This will help log analysis significantly, especially in MM2 mode.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)