[ https://issues.apache.org/jira/browse/KAFKA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671433#comment-15671433 ]
ASF GitHub Bot commented on KAFKA-4400: --------------------------------------- GitHub user skyahead opened a pull request: https://github.com/apache/kafka/pull/2143 KAFKA-4400: Enabling configurable prefix for sink connectors' consume… …r group names. Author: Tianji Li <skyah...@gmail.com> Reviewers: Ewen Cheslack-Postava <m...@ewencp.org> You can merge this pull request into a Git repository by running: $ git pull https://github.com/skyahead/kafka KAFKA4400 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2143.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2143 ---- ---- > 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)