Eran Levy created KAFKA-10643:
---------------------------------
Summary: Static membership - repetitive PreparingRebalance with
updating metadata for member reason
Key: KAFKA-10643
URL: https://issues.apache.org/jira/browse/KAFKA-10643
Project: Kafka
Issue Type: Bug
Components: streams
Affects Versions: 2.6.0
Reporter: Eran Levy
Kafka streams 2.6.0, brokers version 2.6.0. Kafka nodes are healthy, kafka
streams app is healthy.
Configured with static membership.
Every 10 minutes (I assume cause of topic.metadata.refresh.interval.ms), I see
the following group coordinator log:
INFO [GroupCoordinator 2]: Preparing to rebalance group **-**-stream in state
PreparingRebalance with old generation 12244 (__consumer_offsets-45) (reason:
Updating metadata for member
**-**-stream-11-1-013edd56-ed93-4370-b07c-1c29fbe72c9a)
(kafka.coordinator.group.GroupCoordinator)
and right after that the following log:
INFO [GroupCoordinator 2]: Assignment received from leader for group
**-**-stream for generation 12246 (kafka.coordinator.group.GroupCoordinator)
Looked a bit on the kafka code and Im not sure that I get why such a thing
happening - is this line described the situation that happens here re the
"reason:"?[https://github.com/apache/kafka/blob/7ca299b8c0f2f3256c40b694078e422350c20d19/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L311]
I also dont see it happening too often in other kafka streams applications that
we have.
I dont understand why it happens, it wasn't before I applied static membership
to that kafka streams application (since around 2 weeks ago).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
