[
https://issues.apache.org/jira/browse/HDDS-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-9291:
-----------------------------
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 [~sumitagrawl] [~erose] [~swagle] [~ghuangups]
was:
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, that 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 still manually rescue the blocks on DNs before the container is
closed and actually block deletion triggered).
> Deny block read requests when block is marked as deleted on Datanodes
> ---------------------------------------------------------------------
>
> Key: HDDS-9291
> URL: https://issues.apache.org/jira/browse/HDDS-9291
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Siyao Meng
> Priority: Major
>
> 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 [~sumitagrawl] [~erose] [~swagle] [~ghuangups]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
