You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/09/23 21:28:22 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15517622#comment-15517622 ]
Jason Gustafson commented on KAFKA-3829:
----------------------------------------
[~liquanpei] Going to go ahead and pick this up since the code freeze is just a week out. Let me know if you have time and would rather finish it yourself.
> 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: Liquan Pei
> Priority: Critical
> Labels: documentation
> Fix For: 0.10.1.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)