[
https://issues.apache.org/jira/browse/HADOOP-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285443#comment-14285443
]
Steve Loughran commented on HADOOP-11488:
-----------------------------------------
Based on Thomas's results, +1.
tests against the object stores are always a bit inconsistent, with more
variance across the swift implementations, and given that when you run them
from your desk you are more likely to hit connectivity problems, potentially
brittle.
Yet those same problems will arise in the real worlds, so it's good to
encounter them early.
Thomas: should we be setting {{fs.s3a.multipart.purge}} by default in test runs?
> 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)
