[
https://issues.apache.org/jira/browse/HDFS-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835382#action_12835382
]
Scott Chen commented on HDFS-983:
---------------------------------
Decode every byte of the above filename.
[239, 191, 189, 239, 191, 189, 94, 67, 239, 191, 189, 239, 191, 189, 210, 181,
94, 81, 239, 191, 189, 209, 167, 113, 32, 32, 32, 239, 191, 189, 239, 186, 128,
239, 191, 189, 239, 191, 189, 239, 191, 189, 239, 191, 189, 94, 87, 50, 109,
239, 191, 189, 94, 76, 239, 191, 189, 124, 239, 191, 189, 44, 239, 191, 189,
39, 239, 191, 189, 47, 75, 239, 191, 189, 239, 191, 189, 52, 83, 239, 191, 189,
239, 191, 189, 64, 239, 191, 189, 239, 191, 189, 74, 122, 73, 212, 182, 79,
123, 239, 191, 189, 116, 239, 191, 189, 239, 191, 189, 239, 191, 189, 239, 191,
189, 80, 45, 239, 191, 189, 73, 239, 191, 189, 239, 191, 189, 239, 191, 189,
75, 210, 129, 239, 191, 189, 239, 191, 189, 239, 191, 189, 239, 191, 189]
No null character found. So there may be some other reason causes this.
> 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.
