[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786248#comment-17786248
]
ASF GitHub Bot commented on HDFS-17129:
---------------------------------------
LiuGuH commented on PR #6244:
URL: https://github.com/apache/hadoop/pull/6244#issuecomment-1812047817
>the only place FBR creates problem is at NN side
DN side heartbeat will be blocked untils fbr finished , with large cold data
storage disk in one datanode.
INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sentblock
report 0x587d5aa72264fafd with lease ID 0x979291640945f56 to namenode:
****:8020, containing 42 storage report(s), of which we sent 42. The reports
had 15093613 total blocks and used 42 RPC(s).
>earlier only IBR was under lock or what? what case was the earlier lock
solving?
With [HDFS-16016](https://issues.apache.org/jira/browse/HDFS-16016) , only
IBR was under lock to guarantee ibr atomicity.
Thanks.
> mis-order of ibr and fbr on datanode
> -------------------------------------
>
> Key: HDFS-17129
> URL: https://issues.apache.org/jira/browse/HDFS-17129
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.4.0
> Environment: hdfs3.4.0
> Reporter: liuguanghua
> Assignee: liuguanghua
> Priority: Major
> Labels: pull-request-available
>
> HDFS-16016 , provide new thread to handler IBR. That is a greate improvement.
> But it maybe casue the mis-order of ibr 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]
