[
https://issues.apache.org/jira/browse/KAFKA-8287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826183#comment-16826183
]
Matthias J. Sax commented on KAFKA-8287:
----------------------------------------
Can you elaborate on this proposal? I am not sure if it's Kafka Streams'
responsibility to check if the configuration is correct? Also, it does not
solve the problem across JVMs. Hence, I am wondering if we should address it at
all. Thoughts?
> 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
> 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)
