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

Posted to jira@kafka.apache.org by "Ismael Juma (Jira)" <ji...@apache.org> on 2021/02/25 22:05:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Ismael Juma updated KAFKA-10101:
--------------------------------
    Fix Version/s: 2.8.0

> 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
>            Assignee: Ismael Juma
>            Priority: Major
>             Fix For: 2.8.0
>
>
> 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)