[
https://issues.apache.org/jira/browse/HDFS-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042927#comment-18042927
]
ASF GitHub Bot commented on HDFS-16432:
---------------------------------------
github-actions[bot] commented on PR #3907:
URL: https://github.com/apache/hadoop/pull/3907#issuecomment-3614837493
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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: 20220209-120613.html, image-2022-01-20-15-19-28-384.png
>
> Time Spent: 2h 20m
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
