[jira] [Updated] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake

["Satish Duggana (Jira)" <ji...@apache.org>]

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

Satish Duggana updated KAFKA-15375:
-----------------------------------
    Fix Version/s: 3.7.0
                       (was: 3.6.0)

> When running in KRaft mode, LogManager may creates CleanShutdown file by mistake 
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-15375
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15375
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 3.3.2, 3.4.1, 3.5.1
>            Reporter: Vincent Jiang
>            Assignee: Vincent Jiang
>            Priority: Major
>             Fix For: 3.3.3, 3.4.2, 3.5.2, 3.7.0
>
>
> Consider following sequence when running Kafka in KRaft mode:
>  # A partition log "log1" is created under "logDir1", and some records are appended to it.
>  # Broker crashes. No clean shutdown file is created in "logDir1".
>  # Broker is restarted. BrokerServer.startup is called.
>  # On a different thread, LogManager.startup is called by BrokerMetadataPublisher.
>  # Before LogManager.startup finishing recovering logs under "logDir1", fatal exception is thrown in BrokerServer.startup.
>  # In exception hander, BrokerServer.startup calls LogManager.shutdown. As a result, a clean shutdown file is created under "logDir1"
>  # Broker is restarted again. Due to the clean shutdown file created in step 6, recovery is skipped for logs under "logDir1", which is not right because "logDir1" was not fully recovered in step 5.



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