You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Paul (Jira)" <ji...@apache.org> on 2022/05/09 08:59:00 UTC
[jira] [Commented] (FLINK-27480) KafkaSources sharing the groupId might lead to InstanceAlreadyExistException warning
[ https://issues.apache.org/jira/browse/FLINK-27480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533706#comment-17533706 ]
Fabian Paul commented on FLINK-27480:
-------------------------------------
Merged in
* master: f723242e2249b90da22867fde7f8fa99b3c9de98
* release-1.15: f92da27b486ee555ac70b923fad9ca8784914397
* release-1.14: df7206589f755d90950a3c6d1a986453faae6017
> KafkaSources sharing the groupId might lead to InstanceAlreadyExistException warning
> ------------------------------------------------------------------------------------
>
> Key: FLINK-27480
> URL: https://issues.apache.org/jira/browse/FLINK-27480
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.15.0, 1.14.4, 1.16.0
> Reporter: Fabian Paul
> Assignee: Fabian Paul
> Priority: Major
> Labels: pull-request-available
>
> More and more frequently, users ran into an issue by not correctly configuring the KafkaSource ([https://stackoverflow.com/questions/72026997/flink-instancealreadyexistsexception-while-migrating-to-the-kafkasource)] and setting non-distinguishable groupIds for the source. Internally the used KafkaConsumer tries to register with the metric system and incorporates the groupId as part of the metric, leading to name collision.
> We should update the documentation to explain the situation properly.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)