Return-Path: 
 <hdfs-issues-return-120310-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 3C86318908
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Mon,  4 May 2015 13:34:07 +0000 (UTC)
Received: (qmail 56089 invoked by uid 500); 4 May 2015 13:34:07 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 56023 invoked by uid 500); 4 May 2015 13:34:07 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 56011 invoked by uid 99); 4 May 2015 13:34:06 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2015 13:34:06 +0000
Date: Mon, 4 May 2015 13:34:06 +0000 (UTC)
From: "Rakesh R (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12712822.1399466094000.69899.1430746446846@Atlassian.JIRA>
In-Reply-To: <JIRA.12712822.1399466094000@Atlassian.JIRA>
References: <JIRA.12712822.1399466094000@Atlassian.JIRA>
 <JIRA.12712822.1399466094444@arcas>
Subject: [jira] [Commented] (HDFS-6348) Secondary namenode -  RMI Thread
 prevents JVM from exiting after main() completes
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-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526628#comment-14526628 ] 

Rakesh R commented on HDFS-6348:
--------------------------------

Attached re-based(in latest trunk) patch to get the jenkins report.

> Secondary namenode -  RMI Thread prevents JVM from exiting after main() completes
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-6348
>                 URL: https://issues.apache.org/jira/browse/HDFS-6348
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.3.0
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>         Attachments: HDFS-6348-003.patch, HDFS-6348.patch, HDFS-6348.patch, secondaryNN_threaddump_after_exit.log
>
>
> Secondary Namenode is not exiting when there is RuntimeException occurred during startup.
> Say I configured wrong configuration, due to that validation failed and thrown RuntimeException as shown below. But when I check the environment SecondaryNamenode process is alive. When analysed, RMI Thread is still alive, since it is not a daemon thread JVM is nit exiting. 
> I'm attaching threaddump to this JIRA for more details about the thread.
> {code}
> java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy not found
> 	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1900)
> 	at org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy.getInstance(BlockPlacementPolicy.java:199)
> 	at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.<init>(BlockManager.java:256)
> 	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:635)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:260)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:205)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:695)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: Class com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy not found
> 	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1868)
> 	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1892)
> 	... 6 more
> Caused by: java.lang.ClassNotFoundException: Class com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy not found
> 	at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:1774)
> 	at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1866)
> 	... 7 more
> 2014-05-07 14:27:04,666 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Stopping services started for active state
> 2014-05-07 14:27:04,666 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Stopping services started for standby state
> 2014-05-07 14:31:04,926 INFO org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: STARTUP_MSG: 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)