[ 
https://issues.apache.org/jira/browse/KAFKA-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770491#comment-17770491
 ] 

Arpit Goyal commented on KAFKA-15169:
-------------------------------------

> Another one that comes to my mind is if we have a 
> "<index_unique_name>.delete" file on the disk (because files with delete 
> suffix are removed async) and another one with the same name is created (it 
> would occur second time the entry with same key gets invalidated). It should 
> be a no-op in that case (instead of throwing an error).

[~divijvaidya] This should be similar to what you mentioned long back 
>Another test:
1. Create an index and verify file exists
2. Invalidate the index from cache which will mark it for cleanup i.e. change 
suffix to .deleted
3. Try to fetch the same index from cache, cache will not have it and re-fetch 
it.
4. Invalidate this index.
5. If the cleaner thread is slow, the file in step 2 will still exist
6. When we try to move this new file at step 4 to the same name with deleted, 
verify that it doesn't fail and instead overwrites the file.

> Add tests for RemoteIndexCache
> ------------------------------
>
>                 Key: KAFKA-15169
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15169
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Satish Duggana
>            Assignee: Arpit Goyal
>            Priority: Major
>              Labels: KIP-405
>             Fix For: 3.7.0
>
>
> Follow-up from 
> https://github.com/apache/kafka/pull/13275#discussion_r1257490978



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to