Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 19 Sep 2017 09:11:00 +0000 (UTC)
From: "Weiwei Yang (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.13103195.1505812256000.144934.1505812260272@Atlassian.JIRA>
In-Reply-To: <JIRA.13103195.1505812256000@Atlassian.JIRA>
References: <JIRA.13103195.1505812256000@Atlassian.JIRA> <JIRA.13103195.1505812256351@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-12489) Ozone: OzoneRestClientException
 swallows exceptions which makes client hard to debug failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Sep 2017 09:11:06 -0000

Weiwei Yang created HDFS-12489:
----------------------------------

             Summary: 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


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