[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Egerton updated KAFKA-15676: ---------------------------------- Summary: Scheduled rebalance delay for Connect is unnecessarily triggered when group coordinator bounces (was: Scheduled rebalance delay for Connect is unnecessarily triggered when Kafka cluster bounces) > Scheduled rebalance delay for Connect is unnecessarily triggered when group > coordinator bounces > ----------------------------------------------------------------------------------------------- > > Key: KAFKA-15676 > URL: https://issues.apache.org/jira/browse/KAFKA-15676 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect > Reporter: Chris Egerton > Assignee: Chris Egerton > Priority: Major > > When a Connect worker loses contact with the group coordinator, it > voluntarily gives up (i.e., stops) its assignment of connectors and tasks. > For more context, see KAFKA-9184. > > However, this change in state is not relayed the worker's instance of the > [IncrementalCooperativeAssignor > class|https://github.com/apache/kafka/blob/d144b7ee387308a59e52cbdabc7b66dd3b2926cc/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/distributed/IncrementalCooperativeAssignor.java]. > This has the consequence that, if the group coordinator for a Connect > cluster is unavailable for long enough, all of the workers in cluster will > revoke their assigned connectors and tasks, report that they have been > assigned no connectors and tasks during the next rebalance, and spuriously > trigger the scheduled rebalance delay (since the leader will assume that all > workers should still be running the connectors and tasks that it assigned > during the last rebalance). -- This message was sent by Atlassian Jira (v8.20.10#820010)