hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9887) WebHdfs socket timeouts should be configurable
Date Mon, 07 Mar 2016 16:29:41 GMT

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

Wei-Chiu Chuang commented on HDFS-9887:

I think this patch is not complete -- if for some reason SSL configuration throws an exception,
the socket timeouts will not be configured, even if the connection is supposed to be webhdfs
only, not swebhdfs.

> WebHdfs socket timeouts should be configurable
> ----------------------------------------------
>                 Key: HDFS-9887
>                 URL: https://issues.apache.org/jira/browse/HDFS-9887
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: fs, webhdfs
>         Environment: all
>            Reporter: Austin Donnelly
>            Assignee: Austin Donnelly
>              Labels: easyfix, newbie
>             Fix For: 2.8.0
>         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

View raw message