[KAFKA-16711] highestOffsetInRemoteStorage is not updated after logDir altering within broker

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Assignee: Luke Chen
• Reporter: Luke Chen
• Created: 13/May/24 09:34
• Updated: 28/May/24 16:06
• Resolved: 28/May/24 16:06

Description

We use topicIdPartition as the key for each RLM task. It will cause highestOffsetInRemoteStorage in log not updated after logDir alter completion. The reproducing flow is like this:

 

1. tp-0 locating in dirA is the leader of the partition
2. tp-0 is altering logDir to dirB
3. tp-0 is copying segments to remote storage (note: the log in dirA)
4. The logDir altering for tp-0 is completed
5. remoteLogManager#onLeadershipChange is invoked, copiedOffsetOption is reset to Optional.empty()
6. The copying segments to remote storage in step 3 for tp-0 is completed, updating copiedOffsetOption to new offset, as well as the log#highestOffsetInRemoteStorage. (note: the log in dirA)
7. In the next run of RLMTask, the log will be the one in target dir (dirB), and the log#highestOffsetInRemoteStorage (dirB) will be the default value (-1), which will block the log cleanup operation.

 

Issue Links

• links to: GitHub Pull Request #15947