You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Boyang Chen (JIRA)" <ji...@apache.org> on 2019/04/25 01:06:00 UTC

[jira] [Created] (KAFKA-8287) JVM global map to fence duplicate client id

Boyang Chen created KAFKA-8287:
----------------------------------

             Summary: 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


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)