You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Ankush Bhatiya (Commented) (JIRA)" <ji...@apache.org> on 2012/02/24 22:23:48 UTC

[jira] [Commented] (HADOOP-6254) s3n fails with SocketTimeoutException

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

Ankush Bhatiya commented on HADOOP-6254:
----------------------------------------

Hi, Can we move this fix to hadoop 0.20.2 branch as well, Hive currently works with 0.20.2 branch and we want this fix there too.
                
> 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
>             Fix For: 0.21.0
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira