[
https://issues.apache.org/jira/browse/HDFS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-5368:
------------------------
Attachment: HDFS-5368.patch
Attaching a patch which takes out {{namenode.isInSafeMode()}} out of
{{datanodeMap}} synchronization
> Namenode deadlock during safemode extention
> -------------------------------------------
>
> Key: HDFS-5368
> URL: https://issues.apache.org/jira/browse/HDFS-5368
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Vinay
> Assignee: Vinay
> Priority: Blocker
> Attachments: HDFS-5368.patch, NN-deadlock.zip
>
>
> Namenode entered to safemode during restart
> 1. After restart NN entered to safemode extention.
> 2. During this time deadlock happened between datanode heartbeat and
> SafemodeMonitor() thread.
> Found one Java-level deadlock:
> =============================
> "org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeMonitor@9fe953":
> waiting to lock monitor 0x18c3b42c (object 0x0439c6f8, a java.util.TreeMap),
> which is held by "IPC Server handler 2 on 62212"
> "IPC Server handler 2 on 62212":
> waiting to lock monitor 0x18c3987c (object 0x043849a0, a
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeInfo),
> which is held by
> "org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeMonitor@9fe953"
> Check attached jstack for complete stack
--
This message was sent by Atlassian JIRA
(v6.1#6144)
