[
https://issues.apache.org/jira/browse/KAFKA-19372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956142#comment-17956142
]
Lucas Brutschy commented on KAFKA-19372:
----------------------------------------
The question is, whether we want to completely delete the topology record when
the last member leaves, or just return that we are not subscribed anymore when
the group is empty. Right now, I'm thinking to not remove the topology record,
since otherwise we are changing the behavior of KIP-1071: We'd allow topology
updates without bumping the topology epoch - we don't want to do this. This
would enable simple "offline" updates of the topology, which would be a good
feature to have, but it should play along well with topology epochs.
So for now, let's just not expose "isSubscribed=true" when the group is empty.
> StreamsGroup should not be subscribed to a topic when it is empty
> -----------------------------------------------------------------
>
> Key: KAFKA-19372
> URL: https://issues.apache.org/jira/browse/KAFKA-19372
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Lucas Brutschy
> Priority: Major
>
> We should behave more like a consumer group and make sure to not be
> subscribed to the input topics anymore when the last member leaves the group.
> We don't do this right now because our topology is still initialized even
> after the last member leaves the group.
> This will allow:
> - Offsets to expire and be cleaned up.
> - Offsets to be deleted through admin API calls.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
