[
https://issues.apache.org/jira/browse/HDDS-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016585#comment-18016585
]
Tsz-wo Sze commented on HDDS-13599:
-----------------------------------
bq. I have provided the counter example in my above comments. ...
[~Sammi], do you mean this comment?
-
https://issues.apache.org/jira/browse/HDDS-13599?focusedCommentId=18015754&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18015754
It won't happen anymore if we lock the file resolver as shown in
-
https://issues.apache.org/jira/browse/HDDS-13599?focusedCommentId=18015693&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18015693
> For read/write, the access method will return a FileChannel. For delete, it
> could delete the file and return Void.
As mentioned above, the access method won't return File object anymore. The
callers only see FileChannel objects. It won't happen anymore that (1) thread
A gets a File, (2) thread B moves it to a new path, (3) thread A open the file
with the old path since (1) and (3) are synchronized. Thread B cannot do
anything in between.
> 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: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
