You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Supratim Deka (JIRA)" <ji...@apache.org> on 2019/03/06 11:39:00 UTC
[jira] [Created] (HDDS-1229) Concurrency issues with Background
Block Delete
Supratim Deka created HDDS-1229:
-----------------------------------
Summary: Concurrency issues with Background Block Delete
Key: HDDS-1229
URL: https://issues.apache.org/jira/browse/HDDS-1229
Project: Hadoop Distributed Data Store
Issue Type: Sub-task
Components: Ozone Datanode
Reporter: Supratim Deka
HDDS-1163 takes a simplistic approach to deal with concurrent block deletes on a container,
when the metadata scanner is checking existence of chunks for each block in the Container Block DB.
As part of HDDS-1663 checkBlockDB() just does a retry if any inconsistency is detected during a concurrency window. The retry is expected to succeed because the new DB iterator will not include any of the blocks being processed by the concurrent background delete. If retry fails, then the inconsistency is ignored expecting the next iteration of the metadata scanner will avoid running concurrently with the same container.
This Jira is raised to explore a more predictable (yet simple) mechanism to deal with this concurrency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org