[ https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479811#comment-17479811 ]
qinyuren commented on HDFS-16432: --------------------------------- [~hexiaoqiao] [~tasanuma] Please take a look. > 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 > Labels: pull-request-available > Attachments: image-2022-01-20-15-19-28-384.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > !image-2022-01-20-15-19-28-384.png|width=683,height=132! > 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. > # Ensure that the processing of the same block is in the same write lock. > # Because StorageInfo.addBlock will moves the block to the head of > blockList, so we can collect blocks that have not been reported by delimiter > block. -- 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