[
https://issues.apache.org/jira/browse/KAFKA-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-12981.
---------------------------------
Fix Version/s: 3.0.0
Reviewer: David Jacot
Resolution: Fixed
> Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar
> are read/updated in sync
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-12981
> URL: https://issues.apache.org/jira/browse/KAFKA-12981
> Project: Kafka
> Issue Type: Improvement
> Reporter: Tom Scott
> Assignee: Tom Scott
> Priority: Minor
> Fix For: 3.0.0
>
>
> KIP-734 extends listOffsetRequest to fetch offsets by max timestamp as well
> as by start and end offset. This relies on LogSegment.maxTimestampSoFar and
> LogSegment.offsetOfMaxTimestampSoFar but there is currently no
> synchronisation between the 2 meaning that one could be updated whilst the
> other is being read.
> This ticket ensure that LogSegment.maxTimestampSoFar and
> LogSegment.offsetOfMaxTimestampSoFar are locked on read to ensure
> synchronisation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
