[
https://issues.apache.org/jira/browse/KAFKA-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-13315.
-----------------------------
Fix Version/s: 3.0.1
3.1.0
Resolution: Fixed
merged the PR to trunk and 3.0.
> log layer exception during shutdown that caused an unclean shutdown
> -------------------------------------------------------------------
>
> Key: KAFKA-13315
> URL: https://issues.apache.org/jira/browse/KAFKA-13315
> Project: Kafka
> Issue Type: Bug
> Reporter: Cong Ding
> Assignee: Cong Ding
> Priority: Major
> Fix For: 3.1.0, 3.0.1
>
>
> We have seen an exception caused by shutting down scheduler before shutting
> down LogManager.
> When LogManager was closing partitons one by one, scheduler called to delete
> old segments due to retention. However, the old segments could have been
> closed by the LogManager, which subsequently marked logdir as offline and
> didn't write the clean shutdown marker. Ultimately the broker would take
> hours to restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
