[
https://issues.apache.org/jira/browse/KAFKA-15190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746236#comment-17746236
]
A. Sophie Blee-Goldman commented on KAFKA-15190:
------------------------------------------------
[~jwreschnig] I'm sure we can find someone to pick up the KIP for a
full-fledged fix like I proposed, so no worries – it seems reasonable to me to
for us to just reuse the static membership group.instance.id for the time
being, if it's set, and punt on the generalized feature for now. Would you be
interested in just doing a small PR for this case instead? Happy to review such
a thing if so
> Allow configuring a streams process ID
> --------------------------------------
>
> Key: KAFKA-15190
> URL: https://issues.apache.org/jira/browse/KAFKA-15190
> Project: Kafka
> Issue Type: Wish
> Components: streams
> Reporter: Joe Wreschnig
> Priority: Major
> Labels: needs-kip
>
> We run our Kafka Streams applications in containers with no persistent
> storage, and therefore the mitigation of persisting process ID the state
> directly in KAFKA-10716 does not help us avoid shuffling lots of tasks during
> restarts.
> However, we do have a persistent container ID (from a Kubernetes
> StatefulSet). Would it be possible to expose a configuration option to let us
> set the streams process ID ourselves?
> We are already using this ID as our group.instance.id - would it make sense
> to have the process ID be automatically derived from this (plus
> application/client IDs) if it's set? The two IDs seem to have overlapping
> goals of identifying "this consumer" across restarts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
