[ 
https://issues.apache.org/jira/browse/HDFS-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835669#comment-17835669
 ] 

ASF GitHub Bot commented on HDFS-17458:
---------------------------------------

hfutatzhanghb opened a new pull request, #6717:
URL: https://github.com/apache/hadoop/pull/6717

   ### Description of PR
   
   In [HDFS-16429](https://issues.apache.org/jira/browse/HDFS-16429) we make 
LightWeightResizableGSet to be thread safe, and in 
[HDFS-16511](https://issues.apache.org/jira/browse/HDFS-16511)  we change some 
methods in ReplicaMap to acquire read lock instead of acquiring write lock.
   
   This PR try to remove unnecessary Block_Pool read lock further.
   
   Recently, I performed stress tests on datanodes to measure their read/write 
operations/second.
   
   Before we removing some lock(createRbw、finalizeBlock etc.),  it can only 
achieve ~2K write ops. After optimizing, it can achieve more than 5K write ops.




> Remove unnecessary BP lock in ReplicaMap
> ----------------------------------------
>
>                 Key: HDFS-17458
>                 URL: https://issues.apache.org/jira/browse/HDFS-17458
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 3.4.0
>            Reporter: farmmamba
>            Assignee: farmmamba
>            Priority: Major
>
> In HDFS-16429 we make LightWeightResizableGSet to be thread safe, and in 
> HDFS-16511  we change some methods in ReplicaMap to acquire read lock instead 
> of acquiring write lock.
> This PR try to remove unnecessary Block_Pool read lock further.
> Recently, I performed stress tests on datanodes to measure their read/write 
> operations/second.
> Before we removing some lock,  it can only achieve ~2K write ops. After 
> optimizing, it can achieve more than 5K write ops.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to