You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "José Armando García Sancio (Jira)" <ji...@apache.org> on 2023/01/10 18:20:00 UTC
[jira] [Updated] (KAFKA-14557) Missing .lock file when using metadata.log.dir
[ https://issues.apache.org/jira/browse/KAFKA-14557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
José Armando García Sancio updated KAFKA-14557:
-----------------------------------------------
Fix Version/s: 3.4.0
3.3.3
(was: 3.5.0)
> Missing .lock file when using metadata.log.dir
> ----------------------------------------------
>
> Key: KAFKA-14557
> URL: https://issues.apache.org/jira/browse/KAFKA-14557
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Reporter: José Armando García Sancio
> Assignee: José Armando García Sancio
> Priority: Major
> Fix For: 3.4.0, 3.3.3
>
>
> If the Kafka node is configured to use a metadata.log.dir that is different from the one specified in log.dir or log.dirs, Kafka doesn't create and grab a file lock for the metadata.lor.dir. The log dir lock file is named .lock.
> This makes is possible for multiple Kafka node to use the same metadata log dir at the same time. This is not supported and should not be allowed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)