Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1026709715.343731266441448171.JavaMail.jira@brutus.apache.org>
Date: Wed, 17 Feb 2010 21:17:28 +0000 (UTC)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Assigned: (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 reassigned HDFS-983:
-------------------------------------

    Assignee: dhruba borthakur

> 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.
-
You can reply to this email to add a comment to the issue online.