[
https://issues.apache.org/jira/browse/KAFKA-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985907#comment-17985907
]
Chia-Ping Tsai commented on KAFKA-19428:
----------------------------------------
[~isding_l] thanks for your response. you are right that checked IOException is
thrown only if the time index is not initialized, and the segment having new
timestamp data should initialize the time index already. Please feel free to
close this jira
> 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)
