[
https://issues.apache.org/jira/browse/KAFKA-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936251#comment-16936251
]
Konstantine Karantasis commented on KAFKA-8931:
-----------------------------------------------
Hi [~HeryLong], thanks for reporting on this.
When a connector get reconfigured all its tasks need to restart to make sure
that they read the new updated configuration.
I'm not sure to which tasks you are referring to as "cached" here.
Are you observing a yet undetected side-effect of:
https://issues.apache.org/jira/browse/KAFKA-8869
somehow?
Clarifying which tasks you see getting restarted and what you'd expect with an
example, might help us get on the same page regarding this issue.
Thanks
> PR '#6850' fix issue 'KAFKA-8449', but lead to restart all cached tasks,
> which conflict to the motivation of incremental cooperative rebalancing.
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-8931
> URL: https://issues.apache.org/jira/browse/KAFKA-8931
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.3.0
> Reporter: HeryLong
> Priority: Blocker
> Attachments:
> 0001-just-restart-current-reconfigurated-connectorTask-no-all-cacheds-ones.patch
>
>
> Recently, we are testing Kafka Connect 2.3.0, checking the incremental
> cooperative rebalancing mechanism.
>
> We found that when new connector was putted via REST endpoint, Kafka Connect
> 2.3.0 will restart all cached tasks;
> And the issuse is 'KAFKA-8449', the PR is
> '[#6850|https://github.com/apache/kafka/pull/6850]';
>
> So, the result is, new connector putted will lead to all cached tasks
> restarted, which conflict to the motivation of incremental cooperative
> rebalancing.
>
> Should it just restart the new reconfigurated connector or tasks, not all
> cached ones?
> And I have made a PR, please check it out,
> '[#7348|https://github.com/apache/kafka/pull/7348]'
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
