hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Ryan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-983) NameNode transaction log corruption with bad filename
Date Thu, 18 Feb 2010 21:49:30 GMT

    [ https://issues.apache.org/jira/browse/HDFS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835423#action_12835423
] 

Andrew Ryan commented on HDFS-983:
----------------------------------

Scott: That also assumes that the bytes we have for the files above are what was actually
requested. That might not be the case. We'd really need to get the input data from before
the first transformation to know that, I think. 

> 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.


Mime
View raw message