You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2016/03/02 08:43:18 UTC
[jira] [Comment Edited] (HADOOP-12827) WebHdfs socket timeouts
should be configurable
[ https://issues.apache.org/jira/browse/HADOOP-12827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175208#comment-15175208 ]
Chris Douglas edited comment on HADOOP-12827 at 3/2/16 7:42 AM:
----------------------------------------------------------------
OK. Added a line to {{hdfs-default.xml}} explaining the default unit.
was (Author: chris.douglas):
OK. Added a line to the default explaining the default.
> 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, HADOOP-12827.004.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
(v6.3.4#6332)