Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 82B4BC603 for ; Wed, 2 May 2012 22:39:20 +0000 (UTC) Received: (qmail 24511 invoked by uid 500); 2 May 2012 22:39:20 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 24342 invoked by uid 500); 2 May 2012 22:39:19 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 24124 invoked by uid 99); 2 May 2012 22:39:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 22:39:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 22:39:12 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 53B3842C028 for ; Wed, 2 May 2012 22:38:52 +0000 (UTC) Date: Wed, 2 May 2012 22:38:52 +0000 (UTC) From: "Hudson (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <262567976.19155.1335998332344.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8342) HDFS command fails with exception following merge of HADOOP-8325 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-8342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266975#comment-13266975 ] Hudson commented on HADOOP-8342: -------------------------------- Integrated in Hadoop-Mapreduce-trunk-Commit #2191 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2191/]) HADOOP-8342. HDFS command fails with exception following merge of HADOOP-8325 (tucu) (Revision 1333224) Result = ABORTED tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333224 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java > HDFS command fails with exception following merge of HADOOP-8325 > ---------------------------------------------------------------- > > Key: HADOOP-8342 > URL: https://issues.apache.org/jira/browse/HADOOP-8342 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 2.0.0 > Environment: QE tests on version 2.0.1205010603 > Reporter: Randy Clayton > Assignee: Alejandro Abdelnur > Fix For: 2.0.0 > > Attachments: HDFS-3337.patch > > > We are seeing most hdfs commands in our nightly acceptance tests fail with an exception as shown below. This started with a few hours of the merge of HADOOP-8325 on 4/30/2012 > hdfs --config conf/hadoop/ dfs -ls dirname > ls: `dirname': No such file or directory > 12/05/01 16:57:52 WARN util.ShutdownHookManager: ShutdownHook 'ClientFinalizer' failed, java.lang.IllegalStateException: Shutdown in progress, cannot remove a shutdownHook > java.lang.IllegalStateException: Shutdown in progress, cannot remove a shutdownHook > at org.apache.hadoop.util.ShutdownHookManager.removeShutdownHook(ShutdownHookManager.java:166) > at org.apache.hadoop.fs.FileSystem$Cache.remove(FileSystem.java:2202) > at org.apache.hadoop.fs.FileSystem$Cache.closeAll(FileSystem.java:2231) > at org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer.run(FileSystem.java:2251) > at org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira