Skip to content

feat(inkless): enable AZ parsing for generated client IDs [KC-330]#699

Open
EelisK wants to merge 1 commit into
mainfrom
EelisK/improve-az-parsing
Open

feat(inkless): enable AZ parsing for generated client IDs [KC-330]#699
EelisK wants to merge 1 commit into
mainfrom
EelisK/improve-az-parsing

Conversation

@EelisK

@EelisK EelisK commented Jul 14, 2026

Copy link
Copy Markdown
Member

ClientAZExtractor determines a preferred availability zone (AZ) when the client ID explicitly embeds one. In case of Kafka Connect, the client ID is automatically generated for the worker's internal producers, consumers, and admin clients: the base client ID is concatenated with "-configs", "-offsets", "-statuses", or a UUID.

Prior to this commit, these concatenated strings were incorrectly treated as the availability zones. Now if we find an AZ in the client ID, we try to match it against the configured racks/AZs and only return it if a match is found.

ClientAZExtractor determines a preferred availability zone (AZ) when the
client ID explicitly embeds one. In case of Kafka Connect, the client ID
is automatically generated for the worker's internal producers,
consumers, and admin clients: the base client ID is concatenated with
"-configs", "-offsets", "-statuses", or a UUID.

Prior to this commit, these concatenated strings were incorrectly
treated as the availability zones. Now if we find an AZ in the client
ID, we try to match it against the configured racks/AZs and
only return it if a match is found.
@EelisK EelisK changed the title feat(inkless): enable AZ parsing for generated client IDs feat(inkless): enable AZ parsing for generated client IDs [KC-330] Jul 15, 2026
@EelisK
EelisK marked this pull request as ready for review July 15, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant