Raman Gupta created KAFKA-8966: ---------------------------------- Summary: Stream state does not transition to RUNNING on client, broker consumer group shows RUNNING Key: KAFKA-8966 URL: https://issues.apache.org/jira/browse/KAFKA-8966 Project: Kafka Issue Type: Bug Components: streams Affects Versions: 2.3.0 Reporter: Raman Gupta
I have a Kafka stream that has been running fine until recently. The new behavior I see is that the stream state on the client goes from CREATED to REBALANCING, but never transitions from REBALANCING to RUNNING. However, at the same time, if I look at the offsets of the corresponding consumer group, the consumer group appears to be consuming from the topic and has no lag. And yet, the client never made a state change to RUNNING. This is confirmed by calling `streams.close` on the stream and noting the state change goes from REBALANCING to PENDING_SHUTDOWN instead of RUNNING to PENDING_SHUTDOWN as expected. I use the state change to enable queries on the stream store -- if the state change listener never triggers to the RUNNING state, there is no way to know when the client is available for queries. Yes, I have confirmed its the correct consumer group. Yes, the consumer group has no consumers when I shut down the client stream. -- This message was sent by Atlassian Jira (v8.3.4#803005)