hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12827) WebHdfs socket timeouts should be configurable
Date Fri, 26 Feb 2016 18:42:18 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169503#comment-15169503

Xiaoyu Yao commented on HADOOP-12827:

[~and1000], thanks for the update. A few additional comments:

1. In hdfs-dfault.xml, can rephrase the following into something like "Value is recommended
to followed by a unit specifier.... If no unit specified is given, the default will be milliseconds."

Value is followed by a unit specifier: ns, us, ms, s, m,
2328	    h, d for nanoseconds, microseconds, milliseconds, seconds,
2329	    minutes, hours, days respectively.

2. In WebHDFS.md, I don't think we should put the dfs.webhdfs.socket.connect-timeout and dfs.webhdfs.socket.read-timeout
in the oauth2 table.  Can you add a new section with its own anchor for them? Here is an example:

3. Please update the patch number when you resubmit a new patch and also remove the duplicate
002 patches to avoid confusion.  

> WebHdfs socket timeouts should be configurable
> ----------------------------------------------
>                 Key: HADOOP-12827
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12827
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>         Environment: all
>            Reporter: Austin Donnelly
>            Assignee: Austin Donnelly
>              Labels: easyfix, newbie
>         Attachments: HADOOP-12827.001.patch, HADOOP-12827.002.patch, HADOOP-12827.002.patch,
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> WebHdfs client connections use sockets with fixed timeouts of 60 seconds to connect,
and 60 seconds for reads.
> This is a problem because I am trying to use WebHdfs to access an archive storage system
which can take minutes to hours to return the requested data over WebHdfs.
> The fix is to add new configuration file options to allow these 60s defaults to be customised
in hdfs-site.xml.
> If the new configuration options are not present, the behavior is unchanged from before.

This message was sent by Atlassian JIRA

View raw message