Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 27 Sep 2017 14:55:01 +0000 (UTC)
From: "Weiwei Yang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13103172.1505807433000.215660.1506524101018@Atlassian.JIRA>
In-Reply-To: <JIRA.13103172.1505807433000@Atlassian.JIRA>
References: <JIRA.13103172.1505807433000@Atlassian.JIRA> <JIRA.13103172.1505807433840@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12488) Ozone: OzoneRestClient needs to be
 configuration awareness
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 27 Sep 2017 14:55:07 -0000


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

Weiwei Yang commented on HDFS-12488:
------------------------------------

When working on a fix, I found that it is not necessarily let {{OzoneRestClient}} be configuration awareness, instead we can simply let {{OzoneClientUtils#newHttpClient}} loads configuration from conf files. Uploaded a patch with 1 line code fix. I have tested on a cluster, now timeout can be configured via {{ozone-site.xml}} file. Please kindly review, thanks.

> Ozone: OzoneRestClient needs to be configuration awareness
> ----------------------------------------------------------
>
>                 Key: HDFS-12488
>                 URL: https://issues.apache.org/jira/browse/HDFS-12488
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>              Labels: OzonePostMerge
>
> When I test ozone on a 15 nodes cluster with millions of keys, responses of rest client becomes to be slower. Following call times out after default 5s,
> {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}
> Then I increase the timeout by explicitly setting following property in {{ozone-site.xml}}
> {code}
>  <property>
>     <name>ozone.client.socket.timeout.ms</name>
>     <value>10000</value>
>   </property>
> {code}
> but this doesn't work and rest clients are still created with default *5s* timeout. This needs to be fixed. Just like {{DFSClient}}, we should make {{OzoneRestClient}} to be configuration awareness, so that clients can adjust client configuration on demand. 


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