[
https://issues.apache.org/jira/browse/KAFKA-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985270#comment-17985270
]
Gaurav Narula edited comment on KAFKA-19428 at 6/23/25 9:20 AM:
----------------------------------------------------------------
-Mind if I take this one as well [~chia7712] ?:)-
Edit: nvm, I see Lan is already working on it. Happy to help with the review.
was (Author: gnarula):
Mind if I take this one as well [~chia7712] ?:)
> 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)
