[HDDS-10242] [hsync] Lease recovery failed as "Unable to find the block"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: HDDS-7593
• Labels: pull-request-available
• Assignee: Ashish Kumar
• Reporter: Ashish Kumar
• Created: 30/Jan/24 06:24
• Updated: 10/Feb/24 07:55
• Resolved: 10/Feb/24 07:55

Description

Make ozone.scm.block.size as 10B for fast reproduction

1. Write 5B data (localID = 113750153625600001 allocated)
2. Do hsync
3. Write another 10B data (localID = 113750153625600002 allocated and kept in openFileTable), DN metadata still has only 113750153625600001 block ID with size 5 as data not yet flushed to DN
4. Do lease recover, Client tries to finalize 113750153625600002 block but this block doesn't exist in DN and failed with below error

Unable to find the block. BlockID : conID: 1 locID: 113750153625600002 bcsId: 0

Issue Links

• Discovered while testing: HDDS-7593 Supporting HSync and lease recovery
• links to: GitHub Pull Request #6164