[
https://issues.apache.org/jira/browse/HDFS-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806631#comment-17806631
]
ASF GitHub Bot commented on HDFS-17129:
---------------------------------------
slfan1989 commented on PR #6244:
URL: https://github.com/apache/hadoop/pull/6244#issuecomment-1891335134
We need to discuss how to address the issue described in this pull request,
which is currently blocking the release of hadoop-3.4.0 RC1.
After reading discussions in #5888 and #6244, I've identified two key pull
requests:
#5408 (HDFS-16898. Remove write lock for processCommandFromActor of DataNode
to reduce impact on heartbeat).
#2998 (HDFS-16016. BPServiceActor to provide a new thread to handle IBR).
It may take me a long time to completely solve the issue. My personal
suggestion is to roll back #5408 (HDFS-16898) and #2998 (HDFS-16016).
@ayushtkn @Hexiaoqiao @virajjasani
cc: @LiuGuH @yuanboliu
> 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, 3.3.9, 3.3.6
> Environment: hdfs3.4.0
> Reporter: liuguanghua
> Assignee: liuguanghua
> Priority: Blocker
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
