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 "Stephen O'Donnell (Jira)" <ji...@apache.org> on 2020/02/10 13:11:00 UTC

[jira] [Created] (HDFS-15160) Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock

Stephen O'Donnell created HDFS-15160:
----------------------------------------

             Summary: Allow ReplicaMap and callers of ReplicaMap.replicas to use readLock
                 Key: HDFS-15160
                 URL: https://issues.apache.org/jira/browse/HDFS-15160
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: datanode
    Affects Versions: 3.3.0
            Reporter: Stephen O'Donnell
            Assignee: Stephen O'Donnell


Now we have HDFS-15150, we can start to move some DN operations to use the read lock rather than the write lock to improve concurrence. The first step is to make the changes to ReplicaMap, as many other methods make calls to it.

This Jira switches read operations against the volume map to use the readLock rather than the write lock.

Additionally, some methods make a call to replicaMap.replicas() (eg getBlockReports, getFinalizedBlocks, deepCopyReplica) and only use the result in a read only fashion, so they can also be switched to using a readLock. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org