[
https://issues.apache.org/jira/browse/KAFKA-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721546#comment-17721546
]
A. Sophie Blee-Goldman commented on KAFKA-14981:
------------------------------------------------
Have we resolved all the known issues with static membership? IIRC there were
some that required broker-side changes, could we accidentally introduce
correctness-related bugs in Streams applications running against older
clusters?
Maybe I'm being paranoid, but I thought we had begun to recommend against using
static membership in Streams (due to the above and/or general stability issues,
though perhaps most/all of those have been sorted out by now – do we know?)
> Set `group.instance.id` in streams consumer so that rebalance will not happen
> if a instance is restarted
> --------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-14981
> URL: https://issues.apache.org/jira/browse/KAFKA-14981
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Hao Li
> Priority: Minor
>
> `group.instance.id` enables static membership so that if a consumer is
> restarted within `session.timeout.ms`, rebalance will not be triggered and
> originally assignment can be returned directly from broker. We can set this
> id in Kafka streams using `threadId` so that no rebalance is trigger within
> `session.timeout.ms`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
