[KAFKA-15388] Handle topics that were having compaction as retention earlier are changed to delete only retention policy and onboarded to tiered storage.

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.9.0
• Assignee: Arpit Goyal
• Reporter: Satish Duggana
• Created: 21/Aug/23 14:14
• Updated: 13/Jun/24 00:53

Description

Context: https://github.com/apache/kafka/pull/13561#discussion_r1300055517

 
There are 3 paths I looked at:

• When data is moved to remote storage (1)
• When data is read from remote storage (2)
• When data is deleted from remote storage (3)

(1) Does not have a problem with compacted topics. Compacted segments are uploaded and their metadata claims they contain offset from the baseOffset of the segment until the next segment's baseOffset. There are no gaps in offsets.
(2) Does not have a problem if a customer is querying offsets which do not exist within a segment, but there are offset after the queried offset within the same segment. However, it does have a problem when the next available offset is in a subsequent segment.
(3) For data deleted via DeleteRecords there is no problem. For data deleted via retention there is no problem.
 
I believe the proper solution to (2) is to make tiered storage continue looking for the next greater offset in subsequent segments.

Steps to reproduce the issue:

// TODO (christo)

Issue Links

• is a child of: KAFKA-16947 Kafka Tiered Storage V2
• is blocked by: KAFKA-16088 Not reading active segments when RemoteFetch return Empty Records.
• relates to: KAFKA-15301 [Tiered Storage] Historically compacted topics send request to remote for active segment during consume
• links to: GitHub Pull Request #15060