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

Handle thread-id random switch on JVM for KStream

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.0
    • Component/s: streams
    • Labels:
      None

      Description

      Currently we are potentially at risk by being bite for interleaving stream thread ids. It is because we share the same init config number when two stream instances happen to be scheduled under one JVM. This would be bad scenario because we could have different thread-ids throughout restarts, which invalidates static membership.

      For example for once our thread id assigned were 1,2,3,4 for instance A and 5, 6, 7, 8 for instance B. On the restart of both instances, the same atomic update could be applied as 1,3,5,7 for A and 2,4,6,8 for B, which changes their group.instance.ids.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              bchen225242 Boyang Chen
              Reporter:
              bchen225242 Boyang Chen

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment