kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4400) Prefix for sink task consumer groups should be configurable
Date Wed, 16 Nov 2016 19:53:59 GMT

    [ 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:


    KAFKA-4400: Enabling configurable prefix for sink connectors' consume…

    …r group names.
    Author: Tianji Li <skyahead@gmail.com>
    Reviewers: Ewen Cheslack-Postava <me@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:


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:
>            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

View raw message