[
https://issues.apache.org/jira/browse/HADOOP-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787830#action_12787830
]
Andrew Hitchcock commented on HADOOP-6254:
------------------------------------------
We could catch both of these Exceptions individually, but it is conceivable
that other non-fatal IOExceptions could occur when reading from S3. I'd prefer
having it catch all IOExceptions (which encompass SocketTimeoutException and
SocketException).
> 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.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.
