[
https://issues.apache.org/jira/browse/HADOOP-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282092#comment-14282092
]
Hadoop QA commented on HADOOP-11488:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12692998/HADOOP-11488.patch
against trunk revision 24315e7.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws:
org.apache.hadoop.ha.TestZKFailoverControllerStress
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5425//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5425//console
This message is automatically generated.
> 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
>
>
> 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)
