hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11488) Difference in default connection timeout for S3A FS
Date Tue, 27 Jan 2015 10:45:41 GMT

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

Steve Loughran commented on HADOOP-11488:
-----------------------------------------

although option #2 is "purest", I'm going to recommend #1. Why? if creating the test FS fails,
then trying to do it again in the teardown is simply going to create more problems

-steve

> Difference in default connection timeout for S3A FS
> ---------------------------------------------------
>
>                 Key: HADOOP-11488
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11488
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.6.0
>            Reporter: Harsh J
>            Assignee: Daisuke Kobayashi
>            Priority: Minor
>         Attachments: HADOOP-11488.patch, HADOOP-11488.patch
>
>
> The core-default.xml defines fs.s3a.connection.timeout as 5000, and the code under hadoop-tools/hadoop-aws
defines it as 50000.
> We should update the former to 50s so it gets taken properly, as we're also noticing
that 5s is often too low, especially in cases such as large DistCp operations (which fail
with {{Read timed out}} errors from the S3 service).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message