[
https://issues.apache.org/jira/browse/HDFS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835470#action_12835470
]
Todd Lipcon commented on HDFS-983:
----------------------------------
Do you think we should reopen HADOOP-6522 to commit to branch-20, then? I don't
know that it caused your particular bug, but certainly seems possible.
This also seems pretty reproducible. Anyone have time to try creating some
files with null bytes on a test cluster?
> 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.
