You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2010/02/17 22:15:27 UTC
[jira] Created: (HDFS-983) NameNode transaction log corruption with
bad filename
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
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.
[jira] Resolved: (HDFS-983) NameNode transaction log corruption
with bad filename
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ 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