[
https://issues.apache.org/jira/browse/KAFKA-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Brutschy updated KAFKA-19994:
-----------------------------------
Affects Version/s: 4.1.1
4.0.1
3.9.1
3.8.1
> TaskManager may not close all tasks on task timeouts
> ----------------------------------------------------
>
> Key: KAFKA-19994
> URL: https://issues.apache.org/jira/browse/KAFKA-19994
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 3.8.1, 3.9.1, 4.0.1, 4.1.1
> Reporter: Lucas Brutschy
> Assignee: Lucas Brutschy
> Priority: Blocker
> Fix For: 3.9.2, 4.2.0, 4.0.2, 4.1.2
>
>
> When a {{TimeoutException}} occurs while trying to put multiple active tasks
> back into running, we will add the timed out task back to the state updater,
> so that it gets properly closed during unclean shutdown of the thread.
> However, if we run into a Task timeout (failing to make progress for a long
> time), we will rethrow a StreamsException wrapping the TimeoutException we
> have drained multiple tasks from the state updater, they will be lost, and
> not added back to the state updater, and therefore not be closed correctly.
> The task directories remain locked, causing issues trying to replace the
> stream thread.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
