[
https://issues.apache.org/jira/browse/HDFS-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747724#comment-17747724
]
ASF GitHub Bot commented on HDFS-17121:
---------------------------------------
Hexiaoqiao commented on PR #5888:
URL: https://github.com/apache/hadoop/pull/5888#issuecomment-1652843223
> just one question: do you mean you already have IBR and FBR being
processed asynchronously? or you mean you have
[HDFS-16016](https://issues.apache.org/jira/browse/HDFS-16016) deployed?
Send FBR asynchronously. (Not include IBR, because we didn't meet some
performance issue here).
> if we want to solve the ordering problem by using the same lock for both
IBR and FBR as part of this PR, do we really need
[HDFS-17129](https://issues.apache.org/jira/browse/HDFS-17129) as separate Jira?
+1, if we could solve this issue here, we DO NOT need create another one.
> 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: [email protected]
For additional commands, e-mail: [email protected]
