You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "M. Manna (JIRA)" <ji...@apache.org> on 2018/08/10 07:31:00 UTC

[jira] [Comment Edited] (KAFKA-6701) synchronize Log modification between delete cleanup and async delete

    [ https://issues.apache.org/jira/browse/KAFKA-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575873#comment-16575873 ] 

M. Manna edited comment on KAFKA-6701 at 8/10/18 7:30 AM:
----------------------------------------------------------

[~lindong] I believe this might also be a fix for https://issues.apache.org/jira/browse/KAFKA-6188 . But the issue still occurs on Windows as of 2.11-1.1.0 release.


was (Author: manmedia@gmail.com):
[~lindong] I believe this might also be a fix for https://issues.apache.org/jira/browse/KAFKA-6188 .

> synchronize Log modification between delete cleanup and async delete
> --------------------------------------------------------------------
>
>                 Key: KAFKA-6701
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6701
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Sumant Tambe
>            Assignee: Sumant Tambe
>            Priority: Major
>
> Kafka broker crashes without any evident disk failures 
> From [~becket_qin]: This looks a bug in kafka when topic deletion and log retention cleanup happen at the same time, the log retention cleanup may see ClosedChannelException after the log has been renamed for async deletion.
> The root cause is that the topic deletion should have set the isClosed flag of the partition log to true and the retention should not bother to do the old log segments deletion when the log is closed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)