[
https://issues.apache.org/jira/browse/HDFS-15981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042039#comment-18042039
]
ASF GitHub Bot commented on HDFS-15981:
---------------------------------------
github-actions[bot] commented on PR #2916:
URL: https://github.com/apache/hadoop/pull/2916#issuecomment-3599561558
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.
> Removing redundant block queues will slow down block reporting
> --------------------------------------------------------------
>
> Key: HDFS-15981
> URL: https://issues.apache.org/jira/browse/HDFS-15981
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: zhanghuazong
> Assignee: zhanghuazong
> Priority: Major
> Labels: pull-request-available
> Attachments: HDFS-15981.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the block report satisfies the block distribution strategy, the block is
> removed from the lowredundancyBlocks. But removing the block from the
> lowredundancyBlocks is a redundant operation.
> First, in the patch queue, the block removal operation will be performed in
> the method chooseSourceDatanodes and validateReconstructionWork.
> second, the removal of the block report will only be at the
> QUEUE_REPLICAS_BADLY_DISTRIBUTED level, which is not an accurate operation.
> Finally, when there is a large amount of data in the
> QUEUE_REPLICAS_BADLY_DISTRIBUTED queue, the processing efficiency of the
> block report will be reduced
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
