[KAFKA-15511] Exception not handled correctly if indexFile is corrupted.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0
• Fix Version/s: 3.6.0, 3.7.0
• Component/s: Tiered-Storage
• Assignee: Arpit Goyal
• Reporter: Arpit Goyal
• Created: 27/Sep/23 07:45
• Updated: 02/Oct/23 08:07
• Resolved: 29/Sep/23 10:50

Description

I was simulating a code flow where there is a possibility of inconsistency between RemoteCache and fileStored on disk.

1. OffsetIndex Corrupt File already exist on disk
2. There is no entry exist in the RemoteIndexCache
3. Call getIndexEntry
4. As File already exists on the disk and corrupted , indexSanityCheck will throws "CorruptIndexException"

5. But the code flow in RemoteIndexCache catches only "CorruptRecordException".

Ideally it should catch CorruptIndexException instead of CorruptRecordException.

Impact - Functionality is break on the above code flow , and it will not able to auto-recover and overwriting the corrupted index file.

Check the screenshot attached for more reference.

cc divijvaidya satish.duggana

Issue Links

• is a child of: KAFKA-15420 Kafka Tiered Storage V1
• links to: GitHub Pull Request #14459