[
https://issues.apache.org/jira/browse/HDFS-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220744#comment-17220744
]
Xiaoqiao He commented on HDFS-15641:
------------------------------------
Thanks [~wanghongbing],[~ferhui] for your works here, and sorry for late
response.
{quote}UT passed without your fix. Could you please take a look?{quote}
+1, Just check the added unit test, I found it can pass without other changes.
suggest to add annotation or it will be confused to other guys. we should
create bpThread after lifelineSender start if possible.
{quote}cluster = new
MiniDFSCluster.Builder(conf).numDataNodes(3).build();{quote}
For added unit test, is it OK with one datanode?
We can submit addendum patch to improve it if possible since v003 has committed.
> DataNode could meet deadlock if invoke refreshNameNode
> ------------------------------------------------------
>
> Key: HDFS-15641
> URL: https://issues.apache.org/jira/browse/HDFS-15641
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Hongbing Wang
> Assignee: Hongbing Wang
> Priority: Critical
> Fix For: 3.4.0
>
> Attachments: HDFS-15641.001.patch, HDFS-15641.002.patch,
> HDFS-15641.003.patch, deadlock.png, deadlock_fixed.png, jstack.log
>
>
> DataNode could meet deadlock when invoke `hdfs dfsadmin -refreshNamenodes
> hostname:50020` to register a new namespace in federation env.
> The jstack is shown in jstack.log
> The specific process is shown in Figure deadlock.png
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
