You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Xu Shao Hong (Jira)" <ji...@apache.org> on 2022/10/08 08:34:00 UTC
[jira] [Created] (HDDS-7300) Conflict between full data scan and block deletion
Xu Shao Hong created HDDS-7300:
----------------------------------
Summary: Conflict between full data scan and block deletion
Key: HDDS-7300
URL: https://issues.apache.org/jira/browse/HDDS-7300
Project: Apache Ozone
Issue Type: Bug
Reporter: Xu Shao Hong
Assignee: Xu Shao Hong
We have enabled the full data scan and found that one container is marked as unhealthy due to the conflict between full data scan and block deletion.
The block deleting service first deletes the block and then updates the DB, while the data scan first scans the DB and then checks the existence of the blocks.
*The block deleting service has a write lock during the process but the data scan has no read lock to avoid the conflict.*
Even by double checking the block if the block is still in the block-data table when the block is not found on the FS for the first time, the problem still happens. The flush time of DB batch operation is not predictable, so the direct second retrieval may not be a good solution as we cannot determine a fixed delay that could guarantee every batch could be flushed after this delay.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org