[ https://issues.apache.org/jira/browse/HDFS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835434#action_12835434 ]
Scott Chen commented on HDFS-983: --------------------------------- Just discussed with Rodrigo and Dmytro. The filename may be decoded so it loses all the null characters. So this problem may still related to HADOOP-6522. > 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.