[
https://issues.apache.org/jira/browse/KAFKA-19510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007221#comment-18007221
]
Lucas Brutschy edited comment on KAFKA-19510 at 7/15/25 12:57 PM:
------------------------------------------------------------------
EDIT: Sorry - this is what happens with flaky bugs. I have confirmed that this
also happens on 3.9.
was (Author: JIRAUSER302322):
I have confirmed that this happens after:
[https://github.com/apache/kafka/commit/571f50817c]
and does not happen before the commit.
Seems the fix in https://issues.apache.org/jira/browse/KAFKA-18498 wasn't
sufficient.
> Kafka Streams does not always release lock when adding or removing threads
> multiple times
> -----------------------------------------------------------------------------------------
>
> Key: KAFKA-19510
> URL: https://issues.apache.org/jira/browse/KAFKA-19510
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 3.9.0
> Reporter: Lucas Brutschy
> Priority: Major
>
> Kafka Streams seems to not always release the state directory lock for all
> tasks, when threads are added / removed.
> It seems this problem is related to
> [https://github.com/apache/kafka/pull/16922].
> Effectively, the old thread (same name, different object) still seems to own
> the task.
> To reproduce, checkout
> https://github.com/lucasbru/kafka/commit/2701dd39fe7df23a123939a1c9e140c849904b5f
> and run `AdjustStreamThreadCountTest >
> shouldAddAndRemoveThreadsMultipleTimes` ... multiple times.
>
> The test was changed to use a stateful topology.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
