Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-12981

Ensure LogSegment.maxTimestampSoFar and LogSegment.offsetOfMaxTimestampSoFar are read/updated in sync

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 3.0.0
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            tom@confluent.io Tom Scott
            tom@confluent.io Tom Scott
            David Jacot David Jacot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: