You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/10/20 16:18:00 UTC
[jira] [Updated] (KAFKA-9145) AbstractCoordinator should respect
retry backoff between rebalances
[ https://issues.apache.org/jira/browse/KAFKA-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Bejeck updated KAFKA-9145:
-------------------------------
Fix Version/s: (was: 2.7.0)
> AbstractCoordinator should respect retry backoff between rebalances
> -------------------------------------------------------------------
>
> Key: KAFKA-9145
> URL: https://issues.apache.org/jira/browse/KAFKA-9145
> Project: Kafka
> Issue Type: Improvement
> Components: consumer, KafkaConnect
> Reporter: Jason Gustafson
> Priority: Major
>
> We hit a situation where the connect worker seems to have been requesting group rejoins repeatedly for some reason. In theory the same thing could happen to the consumer if a user repeatedly changes the subscribed topics in a tight loop. Currently AbstractCoordinator would not backoff in these cases because the rebalances may all be completing successfully. It probably makes sense to enforce a minimum time between locally triggered rebalances in order to avoid overloading the broker with repeated group rebalances.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)