[
https://issues.apache.org/jira/browse/HDFS-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171524#comment-16171524
]
Yiqun Lin commented on HDFS-12489:
----------------------------------
Hi [~cheersyang], thanks for reporting this. Ozone shell commands is used by
users. I have a question in my mind: It's appropriate to show so detailed
exception info in the response content? If we want to root cause the failure,
we can look into the log. So we should ensure exception info is clearly
printed in log. For the client, a short and simple message is okay. How do you
think?
> 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
> Labels: ozoneMerge
> 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]
