[
https://issues.apache.org/jira/browse/KAFKA-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937456#comment-16937456
]
HeryLong commented on KAFKA-8931:
---------------------------------
Hi @Konstantine Karantasis:
I have made a detail log, please check at link :
https://issues.apache.org/jira/browse/KAFKA-8931?focusedCommentId=16936293&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16936293
> 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)
