[
https://issues.apache.org/jira/browse/HADOOP-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256121#comment-15256121
]
Steve Loughran commented on HADOOP-12844:
-----------------------------------------
I've pulled this in to HADOOP-13028
The mechanism is actually simpler than this patch, because those socket
exceptions already handled are IOEs.
All that's needed is
# expand that clause to catch to all IOEs
# move it after the {{EOFException}} as that's the exception we don't want to
retry.
I'm also now counting how often this event happens on a stream.
> Recover when S3A fails on IOException in read()
> -----------------------------------------------
>
> Key: HADOOP-12844
> URL: https://issues.apache.org/jira/browse/HADOOP-12844
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.1, 2.7.2
> Reporter: Pieter Reuse
> Assignee: Pieter Reuse
> Attachments: HADOOP-12844.001.patch
>
>
> This simple patch catches IOExceptions in S3AInputStream.read(byte[] buf, int
> off, int len) and reopens the connection on the same location as it was
> before the exception.
> This is similar to the functionality introduced in S3N in
> [HADOOP-6254|https://issues.apache.org/jira/browse/HADOOP-6254], for exactly
> the same reason.
> Patch developed in cooperation with [~emres].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
