[ 
https://issues.apache.org/jira/browse/HDFS-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747434#comment-17747434
 ] 

ASF GitHub Bot commented on HDFS-17121:
---------------------------------------

LiuGuH commented on PR #5888:
URL: https://github.com/apache/hadoop/pull/5888#issuecomment-1651437873

    And maybe it not a problem.  The FBR will only process the reported block 
list,the replication r will not discard.  FBR 
    finally execute BlockManager.processReportedBlock   method , just as ibr 
addblock does.




> BPServiceActor to provide new thread to handle FBR
> --------------------------------------------------
>
>                 Key: HDFS-17121
>                 URL: https://issues.apache.org/jira/browse/HDFS-17121
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>            Reporter: liuguanghua
>            Priority: Minor
>              Labels: pull-request-available
>
> After HDFS-16016 , it makes ibr in a thread to avoid heartbeat blocking with 
> ibr when require readlock  in Datanode.
>  Now fbr should do as this.   The reason is this:
> (1)heartbeat maybe block because of fbr with readlock in datanode
> (2)fbr will only may return FinalizeCommand 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to