[
https://issues.apache.org/jira/browse/KAFKA-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8306.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
2.1.2
2.0.2
> Ensure consistency of checkpointed log start offset and current log end offset
> ------------------------------------------------------------------------------
>
> Key: KAFKA-8306
> URL: https://issues.apache.org/jira/browse/KAFKA-8306
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Dhruvil Shah
> Priority: Major
> Fix For: 2.0.2, 2.1.2, 2.2.1
>
>
> When initializing a log, we may use the checkpointed log start offset. We
> need to ensure that the log end offset is set consistently with this value
> (i.e. it must be greater than or equal to it). This may not always be true if
> the log data is removed or has become corrupted. As a simple experiment, you
> can try the following steps to reproduce the problem:
> # Write some data to the partition
> # Use DeleteRecords to advance log start
> # Shutdown the broker
> # Delete the log directory
> # Restart the broker
> You will see something like this in the logs:
> {code:java}
> [2019-04-29 11:55:21,259] INFO [Log partition=foo-0, dir=/tmp/kafka-logs]
> Completed load of log with 1 segments, log start offset 10 and log end offset
> 0 in 36 ms (kafka.log.Log){code}
> This may be the cause of KAFKA-8255, but I am not sure yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
