[
https://issues.apache.org/jira/browse/HDFS-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HDFS-12489:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: HDFS-7240
Status: Resolved (was: Patch Available)
I just committed this to the feature branch, thanks for the review [~linyiqun]
and [~anu].
> Ozone: OzoneRestClientException swallows exceptions which makes client hard
> to debug failures
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-12489
> URL: https://issues.apache.org/jira/browse/HDFS-12489
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Blocker
> Labels: ozoneMerge
> Fix For: HDFS-7240
>
> Attachments: HDFS-12489-HDFS-7240.001.patch,
> HDFS-12489-HDFS-7240.002.patch
>
>
> There are multiple try-catch places swallow exceptions when transforming some
> other exception to {{OzoneRestClientException}}. As a result, when client
> runs into such code paths, they lose track of what was going on which makes
> the debug extremely difficult. See below example
> {code}
> bin/hdfs oz -listBucket http://15oz1.fyre.ibm.com:9864/vol-0-84022 -user wwei
> Command Failed : {"httpCode":0,"shortMessage":"Read timed
> out","resource":null,"message":"Read timed
> out","requestID":null,"hostName":null}
> {code}
> the returned message doesn't help much on debugging where and how it reads
> timed out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
