[
https://issues.apache.org/jira/browse/KAFKA-17808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933701#comment-17933701
]
Jhen-Yung Hsu commented on KAFKA-17808:
---------------------------------------
Since the admin is not exposed, it is hard to write a unit test to check the ID.
[https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/errors/DeadLetterQueueReporter.java#L84-L89]
So, I clipped the log to verify the fix in the PR. PTAL.
> InstanceAlreadyExistsException:
> kafka.admin.client:type=app-info,id=connector-dlq-adminclient- when add
> connector with tasks
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17808
> URL: https://issues.apache.org/jira/browse/KAFKA-17808
> Project: Kafka
> Issue Type: Bug
> Components: connect
> Reporter: ignat233
> Assignee: Jhen-Yung Hsu
> Priority: Major
> Attachments: image-2024-10-16-13-00-36-667.png
>
>
> Why do we always create an admin client with the same
> "connector-dlq-adminclient-" value id?
> [https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java#L1008]
> For all other cases, a postfix is added.
> !image-2024-10-16-13-00-36-667.png!
> I get "Error registering AppInfo mbean
> javax.management.InstanceAlreadyExistsException:
> kafka.admin.client:type=app-info,id=connector-dlq-adminclient-." error for
> all tasks.
> It looks like the ConnectorTaskId should be added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
