You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Tom Scott (Jira)" <ji...@apache.org> on 2021/06/22 19:42:00 UTC

[jira] [Created] (KAFKA-12981) Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar are read/updated in sync

Tom Scott created KAFKA-12981:
---------------------------------

             Summary: 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: Sub-task
            Reporter: Tom Scott


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)