Major Description
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.