[
https://issues.apache.org/jira/browse/HDFS-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829425#comment-17829425
]
Xiping Zhang commented on HDFS-16016:
-------------------------------------
[~liuguanghua] Maybe I didn't describe it clearly, the above processing is in
the namenode,
and does not need to be processed in the datanode end. The FBR is to align the
block information of the namenode and datanode history.
Now we can determine that all blocks reported in the DN end have been added to
the namenode end,
but we cannot guarantee that all the added blocks are included in all blocks
reported this time, right?
for 3.3.0 ，Just delete the red box code
!image-2024-03-21-16-20-46-746.png!
> BPServiceActor add a new thread to handle IBR
> ---------------------------------------------
>
> Key: HDFS-16016
> URL: https://issues.apache.org/jira/browse/HDFS-16016
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: JiangHua Zhu
> Assignee: Viraj Jasani
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.3.6
>
> Attachments: image-2023-11-03-18-11-54-502.png,
> image-2023-11-06-10-53-13-584.png, image-2023-11-06-10-55-50-939.png,
> image-2024-03-20-18-31-23-937.png, image-2024-03-21-16-19-33-668.png,
> image-2024-03-21-16-20-46-746.png
>
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Now BPServiceActor#offerService() is doing many things, FBR, IBR, heartbeat.
> We can handle IBR independently to improve the performance of heartbeat and
> FBR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
