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

Posted to jira@kafka.apache.org by "Jun Rao (Jira)" <ji...@apache.org> on 2020/06/04 15:50:00 UTC

[jira] [Commented] (KAFKA-10101) recovery point is advanced without flushing the data after recovery

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

Jun Rao commented on KAFKA-10101:
---------------------------------

[~ijuma] : Could you double check if this is an issue? Thanks.

> recovery point is advanced without flushing the data after recovery
> -------------------------------------------------------------------
>
>                 Key: KAFKA-10101
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10101
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.5.0
>            Reporter: Jun Rao
>            Priority: Major
>
> Currently, in Log.recoverLog(), we set recoveryPoint to logEndOffset after recovering the log segment. However, we don't flush the log segments after recovery. The potential issue is that if the broker has another hard failure, segments may be corrupted on disk but won't be going through recovery on another restart.
> This logic was introduced in KAFKA-5829 since 1.0.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)