hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Demoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11521) Make connection timeout configurable in s3a
Date Sat, 31 Jan 2015 14:48:34 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Demoor updated HADOOP-11521:
    Attachment: HADOOP-11521.001.patch

The socket time is poorly named fs.s3a.connection.timeout. In order to be backwards compatible,
I named the connection timeout: s.s3a.connection.establish.timeout. Is this OK or should we
rename the current connection.timeout to socket.timeout?

> Make connection timeout configurable in s3a 
> --------------------------------------------
>                 Key: HADOOP-11521
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11521
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 2.6.0
>            Reporter: Thomas Demoor
>            Assignee: Thomas Demoor
>            Priority: Minor
>             Fix For: 2.7.0
>         Attachments: HADOOP-11521.001.patch
> Currently in s3a, only the socket timeout is configurable, i.e. how long to wait before
an existing connection is declared dead. The aws sdk has a separate timeout for establishing
a connection. This patch introduces a config option in s3a to pass this on. 

This message was sent by Atlassian JIRA

View raw message