[ https://issues.apache.org/jira/browse/KAFKA-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boyang Chen resolved KAFKA-8287. -------------------------------- Resolution: Invalid We don't want to do it for now because there are existing use cases where `client.id` is expected to be duplicate across different stream instances for request throttling purpose. > JVM global map to fence duplicate client id > ------------------------------------------- > > Key: KAFKA-8287 > URL: https://issues.apache.org/jira/browse/KAFKA-8287 > Project: Kafka > Issue Type: Sub-task > Components: streams > Reporter: Boyang Chen > Assignee: Boyang Chen > Priority: Major > > After change in https://issues.apache.org/jira/browse/KAFKA-8285, the two > stream instances scheduled on same JVM will be mutually affected if they > accidentally assign same client.id, since the thread-id becomes local now. > The solution is to build a global concurrent map for solving conflict if two > threads happen to be having the same client.id. -- This message was sent by Atlassian JIRA (v7.6.3#76005)