You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "A. Sophie Blee-Goldman (Jira)" <ji...@apache.org> on 2021/03/17 23:44:00 UTC

[jira] [Updated] (KAFKA-12288) Remove task-level filesystem locks

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

A. Sophie Blee-Goldman updated KAFKA-12288:
-------------------------------------------
    Fix Version/s: 2.6.3
                   2.7.1
                   2.8.0

> Remove task-level filesystem locks
> ----------------------------------
>
>                 Key: KAFKA-12288
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12288
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: A. Sophie Blee-Goldman
>            Assignee: A. Sophie Blee-Goldman
>            Priority: Major
>             Fix For: 2.8.0, 2.7.1, 2.6.3
>
>
> Since you actually can't run multiple instances of a Kafka Streams application on the same physical state directory, there's really no benefit to the file locks we obtain as part of the task directory locking. The only safety measures we need are to protect between threads within a process, not across processes. The in-memory map of locks should be sufficient for the StateDirectory to be safe.
> So, we should take out all of the file-based locking of task directories. This should allow us to greatly simplify the StateDirectory code, and eliminate the source of some problems we've faced in the past, particularly those finicky FS/OS dependent issues



--
This message was sent by Atlassian Jira
(v8.3.4#803005)