You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Jimmy Wang (Jira)" <ji...@apache.org> on 2025/09/02 02:36:00 UTC

[jira] [Commented] (KAFKA-19661) Streams groups sometimes describe as NOT_READY when STABLE

    [ https://issues.apache.org/jira/browse/KAFKA-19661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017575#comment-18017575 ] 

Jimmy Wang commented on KAFKA-19661:
------------------------------------

Hi [~lucasbru] , if you haven't start to handle this issue yet, maybe I could help. :)

> Streams groups sometimes describe as NOT_READY when STABLE
> ----------------------------------------------------------
>
>                 Key: KAFKA-19661
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19661
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Lucas Brutschy
>            Assignee: Lucas Brutschy
>            Priority: Major
>
> Streams groups sometimes describe as NOT_READY when STABLE. That is, the group is configured and all topics exist, but when you use LIST_GROUP and STREAMS_GROUP_DESCRIBE, the group will show up as not ready.
> The root cause seems to be that [https://github.com/apache/kafka/pull/19802] moved the creation of the soft state configured topology from the replay path to the heartbeat. This way, LIST_GROUP and STREAMS_GROUP_DESCRIBE, which show the snapshot of the last committed offset, may not show the configured topology, and therefore assume that the streams group is NOT_READY instead of STABLE.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)