Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-7018 persist memberId for consumer restart
  3. KAFKA-8287

JVM global map to fence duplicate client id

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Invalid
    • None
    • None
    • streams
    • None

    Description

      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.

      Attachments

        Activity

          People

            bchen225242 Boyang Chen
            bchen225242 Boyang Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: