[
https://issues.apache.org/jira/browse/KAFKA-16452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen updated KAFKA-16452:
------------------------------
Fix Version/s: 3.8.0
> Bound highwatermark offset to range b/w local-log-start-offset and
> log-end-offset
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-16452
> URL: https://issues.apache.org/jira/browse/KAFKA-16452
> Project: Kafka
> Issue Type: Task
> Reporter: Kamal Chandraprakash
> Assignee: Kamal Chandraprakash
> Priority: Major
> Fix For: 3.8.0
>
>
> The high watermark should not go below the local-log-start offset. If the
> high watermark is less than the local-log-start-offset, then the
> [UnifiedLog#fetchHighWatermarkMetadata|https://sourcegraph.com/github.com/apache/kafka@d4caa1c10ec81b9c87eaaf52b73c83d5579b68d3/-/blob/core/src/main/scala/kafka/log/UnifiedLog.scala?L358]
> method will throw the OFFSET_OUT_OF_RANGE error when it converts the offset
> to metadata. Once this error happens, the followers will receive out-of-range
> exceptions and the producers won't be able to produce messages since the
> leader cannot move the high watermark.
> This issue can happen when the partition undergoes recovery due to corruption
> in the checkpoint file and it gets elected as leader before it gets a chance
> to update the HW from the previous leader.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
