[ https://issues.apache.org/jira/browse/HDFS-17454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834841#comment-17834841 ]
ASF GitHub Bot commented on HDFS-17454: --------------------------------------- xiaojunxiang2023 commented on PR #6709: URL: https://github.com/apache/hadoop/pull/6709#issuecomment-2042162376 > Can you add a test for this, considering now we are propagating the real error back to the client. > > I think if the actual error is being thrown in that case on the client side we can live with just the message, rather than having the entire trace. ok, I'll add a test class for this PR later. Besides, It's not HDFSClient that's actually causing an error, but NameNodeFsck, which uses a DFSClient object that doesn't support Kerbeors. And I will submit another PR to solve the NameNodeFsck's bug later. > Fix namenode fsck swallows the exception stacktrace, this can help us to > troubleshooting log. > --------------------------------------------------------------------------------------------- > > Key: HDFS-17454 > URL: https://issues.apache.org/jira/browse/HDFS-17454 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 3.3.6 > Reporter: xiaojunxiang > Priority: Minor > Labels: pull-request-available > Attachments: image-2024-04-05-15-40-37-147.png, > image-2024-04-05-15-41-38-420.png, image-2024-04-07-13-22-22-493.png, > image-2024-04-07-13-22-46-684.png > > > When I used `hdfs fsck /xxx.txt -move`, missing error, but I can't kown the > reason, because the exception stacktrace doesn't append to LOG, original code: > !image-2024-04-05-15-40-37-147.png! > > When I fix it, look, we can see the exception stacktrace: > !image-2024-04-07-13-22-22-493.png! > !image-2024-04-07-13-22-46-684.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org