You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "qinyuren (Jira)" <ji...@apache.org> on 2022/09/28 07:48:00 UTC
[jira] [Updated] (HDFS-16784) replace readLock with writeLock in #DatanodeAdminBackoffMonitor.scanDatanodeStorage
[ https://issues.apache.org/jira/browse/HDFS-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
qinyuren updated HDFS-16784:
----------------------------
Summary: replace readLock with writeLock in #DatanodeAdminBackoffMonitor.scanDatanodeStorage (was: use write lock in #DatanodeAdminBackoffMonitor.scanDatanodeStorage)
> replace readLock with writeLock in #DatanodeAdminBackoffMonitor.scanDatanodeStorage
> -----------------------------------------------------------------------------------
>
> Key: HDFS-16784
> URL: https://issues.apache.org/jira/browse/HDFS-16784
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: qinyuren
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-09-28-15-37-24-622.png
>
>
> In #DatanodeAdminBackoffMonitor.scanDatanodeStorage, it uses a read lock to protect the function #isBlockReplicatedOk.
> But we found that the function #isBlockReplicatedOk may update the #neededReconstruction under certain conditions.
> !image-2022-09-28-15-37-24-622.png!
> Should we replace the read lock with write lock?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org