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 "Andrew Hitchcock (JIRA)" <ji...@apache.org> on 2009/12/09 01:31:18 UTC

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

     [ https://issues.apache.org/jira/browse/HADOOP-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Hitchcock updated HADOOP-6254:
-------------------------------------

    Attachment: HADOOP-6254-2.txt

New version of the patch. The only difference between the last patch is the addition of two lines of comments to address Tom's concerns.

> 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.