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 "Thomas Demoor (JIRA)" <ji...@apache.org> on 2015/01/31 15:48:34 UTC

[jira] [Updated] (HADOOP-11521) Make connection timeout configurable in s3a

     [ 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
(v6.3.4#6332)