[
https://issues.apache.org/jira/browse/HDDS-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762029#comment-17762029
]
Chung En Lee edited comment on HDDS-9233 at 9/5/23 10:38 AM:
-------------------------------------------------------------
Hi [~deveshsingh] , I think I resolved this issue by the
[patch|https://github.com/apache/ozone/pull/5093]. Can you review it?
The consistent between cache and DB cause the bug.
was (Author: JIRAUSER281449):
Hi [~deveshsingh] , I think I resolved this issue by the
[patch|https://github.com/apache/ozone/pull/5093]. Can you review it?
The consistent between cache and DB causes the bug.
> Investigate whether listStatus() is correctly iterating cache
> -------------------------------------------------------------
>
> Key: HDDS-9233
> URL: https://issues.apache.org/jira/browse/HDDS-9233
> Project: Apache Ozone
> Issue Type: Task
> Components: OM
> Reporter: Siyao Meng
> Assignee: Devesh Kumar Singh
> Priority: Critical
>
> It has come to my attention that the cleanup() method in TestOzoneFileSystem
> (in CI integration (filesystem)), which is triggered after EACH test method
> is incredibly flaky.
> However, when I add a call to wait for double buffer flush, it no longer
> seems flaky:
> https://github.com/apache/ozone/pull/5175/commits/72c297d24a27bd6f334979f70a7a927fc03d8114
> I suspect ofs/o3fs listStatus("/") is not correctly iterating cache.
> Otherwise it should be strongly consistent -- any file deletion should be
> immediately reflected to this or other clients.
--
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
