[
https://issues.apache.org/jira/browse/HADOOP-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787848#action_12787848
]
Hadoop QA commented on HADOOP-6254:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12427397/HADOOP-6254-2.txt
against trunk revision 888565.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/23/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/23/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/23/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/23/console
This message is automatically generated.
> s3n fails with SocketTimeoutException
> -------------------------------------
>
> Key: HADOOP-6254
> URL: https://issues.apache.org/jira/browse/HADOOP-6254
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 0.18.3, 0.19.2, 0.20.1
> Reporter: Andrew Hitchcock
> Assignee: Andrew Hitchcock
> Attachments: HADOOP-6254-2.txt, HADOOP-6254.diff, HADOOP-6254.diff
>
>
> If a user's map function is CPU intensive and doesn't read from the input
> very quickly, compounded by the buffering of input, then S3 might think the
> connection has been lost and will close the connection. Then when the user
> attempts to read from the input again, they'll receive a
> SocketTimeoutException and the task will fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
