sanghyeok An created KAFKA-21217:
------------------------------------
Summary: Ignored client-side rack assignment tags can prevent
Streams protocol clients from starting
Key: KAFKA-21217
URL: https://issues.apache.org/jira/browse/KAFKA-21217
Project: Kafka
Issue Type: Bug
Reporter: sanghyeok An
Assignee: sanghyeok An
With the Streams protocol, the assignment tag list is determined by server-side
configuration:
* Broker default: {{group.streams.rack.aware.assignment.tags}}
* Per-group override: {{streams.rack.aware.assignment.tags}}
The coordinator passes this list to the custom assignor. Clients provide their
tag values through {{{}client.tag.*{}}}, while the client-side
{{rack.aware.assignment.tags}} configuration is documented as ignored.
However, {{StreamsConfig}} still checks whether every tag in the client-side
list is present. For example, even if the server uses {{{}zone{}}}, the
following client configuration fails during construction because
{{client.tag.cluster}} is missing:
* group.protocol=streams
* client.tag.zone=seoul
* rack.aware.assignment.tags=cluster
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
