[
https://issues.apache.org/jira/browse/KAFKA-12996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram updated KAFKA-12996:
-----------------------------------
Fix Version/s: 2.7.2
Affects Version/s: 2.7.1
> OffsetOutOfRange not handled correctly for diverging epochs when fetch offset
> less than leader start offset
> -----------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-12996
> URL: https://issues.apache.org/jira/browse/KAFKA-12996
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.8.0, 2.7.1
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 3.0.0, 2.7.2, 2.8.1
>
>
> {color:#24292e}If fetchOffset < startOffset, we currently throw
> OffsetOutOfRangeException when attempting to read from the log in the regular
> case. But for diverging epochs, we return Errors.NONE with the new leader
> start offset, hwm etc.. ReplicaFetcherThread throws OffsetOutOfRangeException
> when processing responses with Errors.NONE if the leader's offsets in the
> response are out of range and this moves the partition to failed state. We
> should add a check for this case when processing fetch requests and ensure
> OffsetOutOfRangeException is thrown regardless of epochs.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
