[
https://issues.apache.org/jira/browse/HDDS-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016415#comment-18016415
]
Sammi Chen edited comment on HDDS-13599 at 8/27/25 8:24 AM:
------------------------------------------------------------
[~szetszwo] , I have provided the counter example in my above comments. I
think we have some understanding gap here. Please ping me when you have time.
I would like to clarify the situation and resolve it asap.
I know the lock can help between one chunk reader and another replica deletion
thread, but in the multiple chunk readers case, some slower chunk reader will
find file is already deleted before it retries to acquire any lock.
was (Author: sammi):
[~szetszwo] , I have provided the counter example in my above comments. I
think we have some understanding gap here. Please ping me when you have time.
I would like to clarify the situation and resolve it asap.
I know the lock can help between one chunk reader and another replica deletion
thread, but in the multiple chunk readers cases, some slower chunk reader will
find file is already deleted before it retries to acquire any lock.
> Take write Lock of all block files before a container replica directory is
> deleted
> ----------------------------------------------------------------------------------
>
> Key: HDDS-13599
> URL: https://issues.apache.org/jira/browse/HDDS-13599
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sammi Chen
> Priority: Major
> Attachments: screenshot-1.png
>
>
> To avoid interim read failure caused by block file deleted during container
> replica directory deletion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
