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 Wed, 02 Mar 2016 07:19:18 GMT

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

Xiaoyu Yao commented on HADOOP-12827:

Thanks [~chris.douglas] for updating the patch. 

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."
bq. The user should always provide a unit, as Configuration::getTimeDuration complains if
it is not provided. Would you mind if the default unit remained unspecified?

I would suggest having the expected behavior documented when time unit unspecified. Otherwise,
we should add a different version of Configuration::getTimeDuration() that does not take default
unit parameter and throw exception instead of only logging a warn. 

> 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,
HADOOP-12827.002.patch, HADOOP-12827.003.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