[
https://issues.apache.org/jira/browse/KAFKA-15190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743313#comment-17743313
]
A. Sophie Blee-Goldman commented on KAFKA-15190:
------------------------------------------------
I would be a bit hesitant to overly rely on the group.instance.id because not
everyone uses or wants static membership, and that config is completely coupled
to the feature. Perhaps we can reuse the group.instance.id as the process id
only if/when static membership is already being used, which would not
necessarily even require a KIP (maybe), but we'd still need to introduce a new
config for the general use case.
It's a bummer because of course, practically speaking, this new config would
have exactly the same meaning as the group.instance.id – a unique, persistent
identifier for each client. It would have been the perfect config for this use
case if not for Kafka's habit of being overly clever about reusing configs to
enable/disable the related feature, in addition to their actual usage.
> 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
>
> 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)
