You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Vincent Jiang (Jira)" <ji...@apache.org> on 2023/08/17 18:42:00 UTC
[jira] [Updated] (KAFKA-15375) When running in KRaft mode, LogManager may creates CleanShutdown file by mistake
[ https://issues.apache.org/jira/browse/KAFKA-15375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Jiang updated KAFKA-15375:
----------------------------------
Description:
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" needs recovery.
> 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
> Reporter: Vincent Jiang
> Priority: Major
>
> 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" needs recovery.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)