hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11488) Difference in default connection timeout for S3A FS
Date Sun, 01 Feb 2015 14:20:35 GMT

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

Hudson commented on HADOOP-11488:
---------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #88 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/88/])
HADOOP-11488. Difference in default connection timeout for S3A FS. Contributed by Daisuke
Kobayashi. (harsh: rev ffc75d6ebe4912f20f4f4870d2a50abbe4557bfa)
* hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md


> 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
>             Fix For: 2.7.0
>
>         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