hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5368) Namenode deadlock during safemode extention
Date Wed, 16 Oct 2013 09:56:41 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinay updated HDFS-5368:
------------------------

    Affects Version/s: 2.2.0
                       3.0.0

> Namenode deadlock during safemode extention
> -------------------------------------------
>
>                 Key: HDFS-5368
>                 URL: https://issues.apache.org/jira/browse/HDFS-5368
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.2.0
>            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)

Mime
View raw message