[HDFS-12489] Ozone: OzoneRestClientException swallows exceptions which makes client hard to debug failures

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: HDFS-7240
• Component/s: ozone
• Labels: ozoneMerge
• Target Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Weiwei Yang
• Reporter: Weiwei Yang
• Created: 19/Sep/17 09:10
• Updated: 26/Apr/18 21:54
• Resolved: 20/Sep/17 02:48

Description

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

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}

the returned message doesn't help much on debugging where and how it reads timed out.