[
https://issues.apache.org/jira/browse/HDFS-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273504#comment-14273504
]
Steve Loughran commented on HDFS-7599:
--------------------------------------
I'd propose
# have a specific subclass of IOE..helps with testing and tracking down
uses/triggers
# link to a (to be written) Hadoop wiki article, the way we do with networking
problems, explaining problem, possible causes, how to start diagnosing
problems. Goal: help people be self-sufficient without reading the source.
Is the filename known at the time this exception is raised?
> Add more information to exception msg when pipeline recovery fails
> ------------------------------------------------------------------
>
> Key: HDFS-7599
> URL: https://issues.apache.org/jira/browse/HDFS-7599
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: dfsclient
> Affects Versions: 2.6.0
> Reporter: Yongjun Zhang
> Assignee: Yongjun Zhang
> Labels: supportability
>
> When pipeline recovery fails with the following exception, can not easily
> identify the associated file and block, propose to add the info for better
> debuggability:
> {code}
> java.io.IOException: All datanodes <...> are bad. Aborting...
> at
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.setupPipelineForAppendOrRecovery(DFSOutputStream.java:1127)
> at
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(DFSOutputStream.java:924)
> at
> org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:486)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
