[jira] [Created] (KAFKA-9895) Truncation request on broker start up may cause OffsetOutOfRangeException

["Boquan Tang (Jira)" <ji...@apache.org>]

Boquan Tang created KAFKA-9895:
----------------------------------

             Summary: Truncation request on broker start up may cause OffsetOutOfRangeException
                 Key: KAFKA-9895
                 URL: https://issues.apache.org/jira/browse/KAFKA-9895
             Project: Kafka
          Issue Type: Bug
    Affects Versions: 2.4.0
            Reporter: Boquan Tang


We have a 4 broker cluster running version 2.4.0.
Upon broker restart, we frequently observe issue like this:
{code}
[2020-04-20 20:36:37,827] ERROR [ReplicaFetcher replicaId=4, leaderId=1, fetcherId=0] Unexpected error occurred during truncation for topic-name-10 at offset 632111354 (kafka.server.ReplicaFetcherThread)
org.apache.kafka.common.errors.OffsetOutOfRangeException: Received request for offset 632111355 for partition active-ads-10, but we only have log segments in the range 0 to 632111354.
{code}

The partition experiencing this issue seems random. Could we actually ignore this kind of error and not put this partition to offline? From what the error log describes, I think once the start up finishes, and the partition catches up with leader, it should be OK to put it back to ISR. Please help me if I'm understanding it incorrectly.

This happens after we updated to 2.4.0, so I'm wondering if it has anything to do with this specific version or not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)