hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-12488) Ozone: OzoneRestClient needs to be configuration awareness
Date Tue, 19 Sep 2017 08:07:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Weiwei Yang reassigned HDFS-12488:

    Assignee: Weiwei Yang

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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message