You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/11/13 00:14:00 UTC

[jira] [Resolved] (KAFKA-3829) Warn that kafka-connect group.id must not conflict with connector names

     [ https://issues.apache.org/jira/browse/KAFKA-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ewen Cheslack-Postava resolved KAFKA-3829.
------------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.10.1.1)
                   0.10.2.0

Issue resolved by pull request 1911
[https://github.com/apache/kafka/pull/1911]

> Warn that kafka-connect group.id must not conflict with connector names
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-3829
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3829
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.1
>            Reporter: Barry Kaplan
>            Assignee: Jason Gustafson
>              Labels: documentation
>             Fix For: 0.10.2.0
>
>
> If the group.id value happens to have the same value as a connector names the following error will be issued:
> {quote}
> Attempt to join group connect-elasticsearch-indexer failed due to: The group member's supported protocols are incompatible with those of existing members.
> {quote}
> Maybe the documentation for Distributed Worker Configuration group.id could be worded:
> {quote}
> A unique string that identifies the Connect cluster group this worker belongs to. This value must be different than all connector configuration 'name' properties.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)