You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/08/12 08:50:00 UTC

[jira] [Resolved] (KAFKA-17310) locking the offline dir can destroy the broker exceptionally

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

Chia-Ping Tsai resolved KAFKA-17310.
------------------------------------
    Resolution: Fixed

push to trunk and 3.9

> locking the offline dir can destroy the broker exceptionally
> ------------------------------------------------------------
>
>                 Key: KAFKA-17310
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17310
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Kuan Po Tseng
>            Priority: Blocker
>             Fix For: 4.0.0, 3.9.0
>
>
> KAFKA-17176 migrated the FileLock to java, and all `IOException` is wrapped by `RuntimeException`. However, LogManager only handles the `IOException` so the the `RuntimeException` will escape from error-catch and then destroy the broker.
> [0] https://github.com/apache/kafka/blob/5d66f8d88cc3121236287157a2d46856dbae4512/core/src/main/scala/kafka/log/LogManager.scala#L273 



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