[HDDS-9291] Deny block read requests when block is marked as deleted on Datanodes - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Add vote

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Task
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
None

Description

Inspired by ~~HDDS-9146~~ – a sneaky data loss issue where the symptom (data loss) doesn't appear until the container is closed, we might want to add a safety on DNs so that as soon as a block is marked as deleted on a DN, the DN should refuse to serve the block right away, and throw an exception back to the client (stating the block is marked deleted on this Ozone Datanode).

This will help us catch data loss issues similar to ~~HDDS-9146~~ much sooner in UTs, integration tests, acceptance tests and even in production (where we could technically manually rescue the blocks on DNs before the container is closed and actually block deletion happened).

cc Sumit Agrawal Ethan Rose Siddharth Wagle George Huang Tsz-wo Sze