[
https://issues.apache.org/jira/browse/KAFKA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803350#comment-15803350
]
Ewen Cheslack-Postava commented on KAFKA-4400:
----------------------------------------------
[~skyahead] Did you see the comments on the PR? I'd love to get this fixed
since anyone deploying multiple Connect clusters on the same Kafka cluster can
be affected by this if they have connectors with the same name in both Connect
clusters. A KIP would probably be super easy and minimal, any interest in
pushing this forward?
> Prefix for sink task consumer groups should be configurable
> -----------------------------------------------------------
>
> Key: KAFKA-4400
> URL: https://issues.apache.org/jira/browse/KAFKA-4400
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.10.1.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
>
> Currently the prefix for creating consumer groups is fixed. This means that
> if you run multiple Connect clusters using the same Kafka cluster and create
> connectors with the same name, sink tasks in different clusters will join the
> same group. Making this prefix configurable at the worker level would protect
> against this.
> An alternative would be to define unique cluster IDs for each connect
> cluster, which would allow us to construct a unique name for the group
> without requiring yet another config (but presents something of a
> compatibility challenge).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
