[
https://issues.apache.org/jira/browse/KAFKA-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825694#comment-16825694
]
ASF GitHub Bot commented on KAFKA-8285:
---------------------------------------
abbccdda commented on pull request #6632: KAFKA-8285 : localize thread id
URL: https://github.com/apache/kafka/pull/6632
Details in the JIRA:
https://issues.apache.org/jira/browse/KAFKA-8285
Basically we want to avoid sharing of atomic updates for thread id with
multiple stream instances on one JVM.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Handle thread-id random switch on JVM for KStream
> -------------------------------------------------
>
> Key: KAFKA-8285
> URL: https://issues.apache.org/jira/browse/KAFKA-8285
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Boyang Chen
> Assignee: Boyang Chen
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
