[
https://issues.apache.org/jira/browse/HDFS-17454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023457#comment-18023457
]
ASF GitHub Bot commented on HDFS-17454:
---------------------------------------
github-actions[bot] commented on PR #6709:
URL: https://github.com/apache/hadoop/pull/6709#issuecomment-3344446670
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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: [email protected]
For additional commands, e-mail: [email protected]
