You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2025/10/08 10:10:00 UTC

[jira] [Assigned] (KAFKA-19510) Kafka Streams does not always release lock when adding or removing threads multiple times

     [ https://issues.apache.org/jira/browse/KAFKA-19510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Brutschy reassigned KAFKA-19510:
--------------------------------------

    Assignee: Nikita Shupletsov

> 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
>            Assignee: Nikita Shupletsov
>            Priority: Major
>
> Kafka Streams seems to not always release the state directory lock for all tasks, when threads are added / removed. 
> 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. 
>  
> I reproduced this on 3.9, 4.0, 4.1, trunk
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)