[
https://issues.apache.org/jira/browse/HDFS-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041402#comment-18041402
]
ASF GitHub Bot commented on HDFS-16023:
---------------------------------------
github-actions[bot] commented on PR #3091:
URL: https://github.com/apache/hadoop/pull/3091#issuecomment-3590739401
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.
> Improve blockReportLeaseId acquisition to avoid repeated FBR
> ------------------------------------------------------------
>
> Key: HDFS-16023
> URL: https://issues.apache.org/jira/browse/HDFS-16023
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When the NameNode receives the data (FBR) from the DataNode, it will put the
> data in the queue (BlockReportProcessingThread#queue), and there will be
> threads processing them thereafter.
> When the DataNode wants to send data (here, FBR) to the NameNode, it will
> first obtain a blockReportLeaseId from the NameNode. If the DataNode data
> already exists in the queue, there is no need to assign a blockReportLeaseId
> to the DataNode again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
