hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11488) Difference in default connection timeout for S3A FS
Date Sat, 31 Jan 2015 18:49:35 GMT

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

Harsh J commented on HADOOP-11488:

Thanks for all the work here Thomas, Steve and Daisuke! Committing to branch-2 and trunk shortly.

> 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

View raw message