muralibasani opened a new pull request, #22873: URL: https://github.com/apache/kafka/pull/22873
Ref : https://issues.apache.org/jira/browse/KAFKA-20609 In tiered storage, a segment with a future record timestamp was never removed from local disk by time-based retention. since its age was computed from that future timestamp — pinning it locally even after it was safely uploaded to remote storage. In this change - introduced ageReferenceMs variable in deleteRetentionMsBreachedSegments() that normally holds largestTimestamp(), but falls back to the segment's lastModified time when the record timestamp is in the future and remote copy is enabled. Already-offloaded segments then age out of local storage as expected. The existing upload-before-delete guard (isSegmentEligibleForDeletion) keeps data safe, and non-tiered logs are unchanged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
