Kamal Chandraprakash 91bd1baff0 KAFKA-16890: Compute valid log-start-offset when deleting overlapping remote segments (#16237) ... The listRemoteLogSegments returns the metadata list sorted by the start-offset. However, the returned metadata list contains all the uploaded segment information including the duplicate and overlapping remote-log-segments. The reason for duplicate/overlapping remote-log-segments cases is explained [here](https://github.com/apache/kafka/blob/trunk/storage/src/main/java/org/apache/kafka/server/log/remote/metadata/storage/RemoteLogLeaderEpochState.java#L103). The list returned by the RLMM#listRemoteLogSegments can contain the duplicate segment metadata at the end of the list. So, while computing the next log-start-offset we should take the maximum of segments (end-offset + 1). Reviewers: Satish Duggana <satishd@apache.org>		2024-06-13 06:30:51 +05:30
..
src	KAFKA-16890: Compute valid log-start-offset when deleting overlapping remote segments (#16237)	2024-06-13 06:30:51 +05:30
.gitignore	…