[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786222#comment-17786222
]
ASF GitHub Bot commented on HDFS-17129:
---------------------------------------
ayushtkn commented on PR #6244:
URL: https://github.com/apache/hadoop/pull/6244#issuecomment-1811994921
I have been reading the comments on the original ticket, and mostly share
same thought as @Hexiaoqiao, the one case in the end mentioned was answered
here, I believe:
https://issues.apache.org/jira/browse/HDFS-16016?focusedCommentId=17783162&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17783162
and the reporter I believe tried without
[HDFS-16898](https://issues.apache.org/jira/browse/HDFS-16898)? In general I
didn't see IBR/FBR chocking at Datanode side, FBR anyway is very low frequency,
the only place FBR creates problem is at NN side, when almost all DN shoot at
one time, there is a logic to handle this scenario as well, Anyway.....
I was under the impression like when a DN pushes a FBR, all the pending IBR
are pushed before? it isn't that the case now?
What is the fix, put both IBR & BR under lock? earlier only IBR was under
lock or what? what case was the earlier lock solving?
I am just curious, I am not gonna merge this in general, will let other
folks involved in the original ticket chase this..
> 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]
