[
https://issues.apache.org/jira/browse/KAFKA-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565164#comment-17565164
]
Greg Harris commented on KAFKA-14067:
-------------------------------------
This bug is addressed by the fix in https://github.com/apache/kafka/pull/11369
> Sink connector override.consumer.group.id can conflict with worker group.id
> ---------------------------------------------------------------------------
>
> Key: KAFKA-14067
> URL: https://issues.apache.org/jira/browse/KAFKA-14067
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.3.0
> Reporter: Greg Harris
> Priority: Minor
>
> Currently there is a validation step for connector names which prevents sink
> connector consumer groups from colliding with the worker group.id.
> There is currently no such validation for consumer.override.group.id that
> would prevent a conflicting connector from being configured, and so it is
> possible to misconfigure a connector in a way that may be damaging to the
> workers themselves.
> Reproduction steps:
> 1. Configure a connect distributed cluster with a certain group.id in the
> worker config.
> 2. Configure a sink connector with consumer.override.group.id having the same
> value as in the worker config
> Expected behavior:
> 1. An error is returned indicating that the consumer.override.group.id is
> invalid
> 2. The connector is not created or started
> Actual behavior:
> 1. No error is returned, and the configuration is otherwise valid.
> 2. The connector is created and starts running.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
