Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <21813496.146191271354333332.JavaMail.jira@thor>
Date: Thu, 15 Apr 2010 13:58:53 -0400 (EDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Resolved: (HDFS-983) NameNode transaction log corruption
 with bad filename
In-Reply-To: <1630440726.343671266441327947.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

dhruba borthakur resolved HDFS-983.
-----------------------------------

    Resolution: Duplicate

I have not seen this problem after we imported the patch from HADOOP-6522. I am going to close this  issue.

> NameNode transaction log corruption with bad filename
> -----------------------------------------------------
>
>                 Key: HDFS-983
>                 URL: https://issues.apache.org/jira/browse/HDFS-983
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.1
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> The SecondaryNamenode is unable to create checkpoints. The stack trace is attached. This is the second time we have seen this issue. Both these occurances happened with unprintable characters in the filename. I am wondering if there is an String-UTF8 encoding problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira