[
https://issues.apache.org/jira/browse/HDFS-15641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216878#comment-17216878
]
Hongbing Wang edited comment on HDFS-15641 at 10/19/20, 4:38 PM:
-----------------------------------------------------------------
{quote}{{ }}{{just wonder if this issue is also in trunk}}
{quote}
yes, it reproduces in trunk. [^HDFS-15641.000.test.patch] uses CyclicBarrier
to control thread execution order to reproduce deadlock.
was (Author: wanghongbing):
{{{quote} }}
{{just wonder if this issue is also in trunk}}
{{{quote}}}
{{yes, it reproduces in trunk. [^HDFS-15641.000.test.patch] uses
}}CyclicBarrier to control thread execution order to reproduce deadlock.
{{}}
> 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
> Attachments: HDFS-15641.000.test.patch, deadlock.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
