[
https://issues.apache.org/jira/browse/KAFKA-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17167.
------------------------------------
Resolution: Duplicate
this will be included by KAFKA-17166
> Moving the flush call inside the read lock when writing truncation
> ------------------------------------------------------------------
>
> Key: KAFKA-17167
> URL: https://issues.apache.org/jira/browse/KAFKA-17167
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Chia-Ping Tsai
> Assignee: Chia Chuan Yu
> Priority: Minor
>
> copy the discussion
> (https://github.com/apache/kafka/pull/16614#discussion_r1683340380) to here
> {quote}
> Consider the following sequence: we take a snapshot of the epoch entries
> here; a new epoch entry is added and is flushed to disk; the scheduler then
> writes the snapshot to disk. This can lead to the case where the leader epoch
> file doesn't contain all entries up to the recovery point.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
