[
https://issues.apache.org/jira/browse/KAFKA-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032762#comment-17032762
]
Boyang Chen commented on KAFKA-9525:
------------------------------------
If you are talking about application level rebalance triggering, after
https://issues.apache.org/jira/browse/KAFKA-9146 we could potentially have
admin client remove one single member to trigger rebalance, which is pretty
convenient.
> Allow explicit rebalance triggering on the Consumer
> ---------------------------------------------------
>
> Key: KAFKA-9525
> URL: https://issues.apache.org/jira/browse/KAFKA-9525
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Reporter: Sophie Blee-Goldman
> Priority: Major
> Labels: needs-kip
>
> Currently the only way to explicitly trigger a rebalance is by unsubscribing
> the consumer. This has two drawbacks: it does not work with static
> membership, and it causes the consumer to revoke all its currently owned
> partitions. Streams relies on being able to enforce a rebalance for its
> version probing upgrade protocol and the upcoming KIP-441, both of which
> should be able to work with static membership and be able to leverage the
> improvements of KIP-429 to no longer revoke all owned partitions.
> We should add an API that will allow users to explicitly trigger a rebalance
> without going through #unsubscribe
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
