You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Paolo Patierno (JIRA)" <ji...@apache.org> on 2017/06/08 07:16:19 UTC

[jira] [Commented] (KAFKA-4400) Prefix for sink task consumer groups should be configurable

    [ https://issues.apache.org/jira/browse/KAFKA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042325#comment-16042325 ] 

Paolo Patierno commented on KAFKA-4400:
---------------------------------------

[~ewencp] I don't see activity on this since few months. I'd like to start to contribute to the Kafka project so this JIRA could be a starting point for doing that. What do you think ? Can you add me to the contributors list so that I can assign JIRAs to myself ?

Thanks,
Paolo.

> 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
>              Labels: newbie
>
> 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.15#6346)