[
https://issues.apache.org/jira/browse/KAFKA-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch updated KAFKA-9145:
---------------------------------
Fix Version/s: (was: 2.6.0)
2.7.0
Since this is not a blocker issue, as part of the 2.6.0 release process I'm
changing the fix version to `2.7.0`. If this is incorrect, please respond and
discuss on the "[DISCUSS] Apache Kafka 2.6.0 release" discussion mailing list
thread.
> 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
> Fix For: 2.7.0
>
>
> 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)
