[
https://issues.apache.org/jira/browse/KAFKA-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036626#comment-17036626
]
Konstantine Karantasis commented on KAFKA-7381:
-----------------------------------------------
I'll close this ticket, given that since [~rhauch]'s last comment
[KIP-415|https://cwiki.apache.org/confluence/display/KAFKA/KIP-415%3A+Incremental+Cooperative+Rebalancing+in+Kafka+Connect]
has landed as the implemented of Incremental Cooperative Rebalance in Connect.
Connect workers can now choose between eager and incremental cooperative
rebalancing, and these options with respect to load balancing should cover the
vast majority of use cases that require a Connect cluster to be deployed. It's
worth saying that is hard to see how load balancing could be completely
disabled if a distributed system needs to be fault tolerant in the presence of
failures on worker nodes.
> Parameterize connector rebalancing behavior
> -------------------------------------------
>
> Key: KAFKA-7381
> URL: https://issues.apache.org/jira/browse/KAFKA-7381
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 1.0.0
> Reporter: Chen He
> Assignee: Chen He
> Priority: Major
>
> I have a question about connector rebalancing issue. Why don't we make it
> option, I mean have a parameter that turn on/off it instead of having it as a
> must?
>
> We can have a parameter like: "connector.rebalancing.enable" parameter and
> make it as "true" by default. It allows users to turn it off if they want.
>
> There are some cases that connector rebalancing is not needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
