Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79DB710BD4 for ; Wed, 16 Oct 2013 09:56:43 +0000 (UTC) Received: (qmail 35821 invoked by uid 500); 16 Oct 2013 09:56:42 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 35792 invoked by uid 500); 16 Oct 2013 09:56:42 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 35771 invoked by uid 99); 16 Oct 2013 09:56:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 09:56:42 +0000 Date: Wed, 16 Oct 2013 09:56:41 +0000 (UTC) From: "Vinay (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-5368) Namenode deadlock during safemode extention MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)