Page History

...

RLM receives a callback and unassigns the partition for leader/follower task, If the delete option is enabled then the leader will stop RLM task and stop processing and it sets all the remote log segment metadata is updated in RLMM by enabling the delete marker. RLMM of that partition with a delete marker and publishes them to RLMM. Controller will eventually delete these segments by using RemoteStorageManager. As the segments are deleted asynchronously, creation of a Controller will not allow topic with the same name later may cause issues because of the existing metadata about the earlier generation of the topic. to be created till all the segments are cleanedup from remote storage.

It was discussed in the community earlier for adding UUID to represent a topic along with the name as part of KIP-516. That This enhancement will be useful to address the issue mentioned here.make deletion of topic partitions in remote storage asynchronously without blocking the creation of topic with the same name even though all the segments are not deleted in  remote storage.   

OffsetForLeaderEpoch

Look into leader epoch checkpoint cache. This is stored in tiered storage and it may be fetched by followers from tiered storage as part of the fetch protocol. 

...