[
https://issues.apache.org/jira/browse/HDFS-17121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786628#comment-17786628
]
ASF GitHub Bot commented on HDFS-17121:
---------------------------------------
LiuGuH opened a new pull request, #5888:
URL: https://github.com/apache/hadoop/pull/5888
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
After [HDFS-16016](https://issues.apache.org/jira/browse/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
### How was this patch tested?
There is no a new test for it. We can use original test case.
> 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]
