[
https://issues.apache.org/jira/browse/KAFKA-19978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Brutschy updated KAFKA-19978:
-----------------------------------
Priority: Major (was: Minor)
> Don't enter running state as long as group is not ready
> --------------------------------------------------------
>
> Key: KAFKA-19978
> URL: https://issues.apache.org/jira/browse/KAFKA-19978
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Lucas Brutschy
> Assignee: Lucas Brutschy
> Priority: Major
> Fix For: 4.2.0
>
>
> Since internal topics are created asynchronous, and we do not want to
> have heartbeats failing, when an application has not yet created its
> internal topics, it remains in NOT_READY, until the internal topics are
> created.
> The way the client-side is implemented right now, the Kafka Streams
> application will still enter RUNNING state with an empty assignment,
> when internal topics are missing. From the outside, it will therefore
> look like the initial set-up of the application has finished, while the
> application is still waiting for the group to become ready.
> This propagetes the state of the group as part of the assignment, so that
> we delay entering a "RUNNING" state until the group has become ready.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
