[HDFS-12488] Ozone: OzoneRestClient timeout is not configurable

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDFS-7240
• Fix Version/s: HDFS-7240
• Component/s: ozone
• Labels: OzonePostMerge
• Target Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Weiwei Yang
• Reporter: Weiwei Yang
• Created: 19/Sep/17 07:50
• Updated: 26/Apr/18 21:54
• Resolved: 28/Sep/17 22:47

Description

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,

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}

Then I increase the timeout by explicitly setting following property in ozone-site.xml

 <property>
    <name>ozone.client.socket.timeout.ms</name>
    <value>10000</value>
  </property>

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.