You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2017/09/19 07:51:00 UTC
[jira] [Created] (HDFS-12488) Ozone: OzoneRestClient has no notion
of configuration
Weiwei Yang created HDFS-12488:
----------------------------------
Summary: Ozone: OzoneRestClient has no notion of configuration
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
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org