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

["Chia-Ping Tsai (Jira)" <ji...@apache.org>]

Chia-Ping Tsai created KAFKA-19428:
--------------------------------------

             Summary: 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: Chia-Ping Tsai


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)