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

Posted to dev@kafka.apache.org by "Lan Ding (Jira)" <ji...@apache.org> on 2025/06/25 09:03:00 UTC

[jira] [Resolved] (KAFKA-19428) IOException during writing max timestamp should not be ignored

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

Lan Ding resolved KAFKA-19428.
------------------------------
    Resolution: Not A Problem

> IOException during writing max timestamp should not be ignored
> --------------------------------------------------------------
>
>                 Key: KAFKA-19428
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19428
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Lan Ding
>            Priority: Minor
>
> this is similar to KAFKA-19221. The IOException caused by writing max timestamp is currently ignored.
>  
> {code:java}
>         if (maxTimestampAndOffsetSoFar != TimestampOffset.UNKNOWN)
>             Utils.swallow(LOGGER, Level.WARN, "maybeAppend", () -> timeIndex().maybeAppend(maxTimestampSoFar(), shallowOffsetOfMaxTimestampSoFar(), true));
> {code}
>  
> That could be an issue since we assume the last entry is the max timestamp after restarting. If the write fails, the loading log should re-build the index to ensure it catches the "correct" max timestamp.



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