[
https://issues.apache.org/jira/browse/KAFKA-15190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744288#comment-17744288
]
Matthias J. Sax edited comment on KAFKA-15190 at 7/18/23 6:22 PM:
------------------------------------------------------------------
One more thing: the `process.id` is actually only used as part of the
`client.id` iff not `client.id` config is set. – Hence, setting the `client.id`
should avoid the issue of task shuffling (and the rebalance in itself should
not be an issue, as it's cheap)?
was (Author: mjsax):
One more thing: the `process.id` is actually only used as part of the
`client.id` iff not `client.id` config is set. – Hence, setting the `client.id`
should avoid the issue of rebalancing (and task shuffling)?
> 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)
