[KAFKA-8285] Handle thread-id random switch on JVM for KStream

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Component/s: streams
• Assignee: Boyang Chen
• Reporter: Boyang Chen
• Created: 24/Apr/19 19:02
• Updated: 03/May/19 00:17
• Resolved: 03/May/19 00:17

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.

Issue Links

• Blocked: KAFKA-8284 Enable static membership on KStream
• links to: GitHub Pull Request #6632
• mentioned in: Page Loading...