[ 
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

qinyuren updated HDFS-16432:
----------------------------
    Description: 
!image-2022-01-20-15-19-28-384.png|width=652,height=126!

In our cluster, namenode block report will held write lock for a long time if 
the storage block number more than 100000. So we want to add a yield mechanism 
in block reporting process to avoid holding write lock too long.

  was:!image-2022-01-20-15-19-28-384.png|width=652,height=126!


> Namenode block report add yield to avoid holding write lock too long
> --------------------------------------------------------------------
>
>                 Key: HDFS-16432
>                 URL: https://issues.apache.org/jira/browse/HDFS-16432
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: qinyuren
>            Priority: Major
>         Attachments: image-2022-01-20-15-19-28-384.png
>
>
> !image-2022-01-20-15-19-28-384.png|width=652,height=126!
> In our cluster, namenode block report will held write lock for a long time if 
> the storage block number more than 100000. So we want to add a yield 
> mechanism in block reporting process to avoid holding write lock too long.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to