[jira] [Comment Edited] (HDFS-12489) Ozone: OzoneRestClientException swallows exceptions which makes client hard to debug failures

["Anu Engineer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171978#comment-16171978 ] 

Anu Engineer edited comment on HDFS-12489 at 9/19/17 4:22 PM:
--------------------------------------------------------------

Thanks for filing this issue. Making this a blocker since the ability to debug issue easily is critical when Ozone gets used.

[~linyiqun] Shall file another JIRA to support LOG in the Client path, where we can actually add these LOG messages to the DEBUG output. 

From a very personal point of view, since we are testing ozone this helps. I completely understand your point, but can we put that in via next patch? if you are ok with that, I am +1 on this and fixing the verbosity via next patch.




was (Author: anu):
Thanks for filing this issue. Making this a blocker since the ability to debug issue easily is critical when Ozone gets used.


> 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
>         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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org