[
https://issues.apache.org/jira/browse/HADOOP-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171671#comment-15171671
]
Steve Loughran commented on HADOOP-12844:
-----------------------------------------
I'm looking very closely at HADOOP-12444 right now: lazy seek; this proposes
postponing opening the connection until the first read.
Once that's in I think the retry operation might need to go to the read() call.
There's another issue here: we should be adding support for retry policies,
rather than trying to implement logic unique to s3a, even ift's just retry once.
> S3A fails on IOException
> ------------------------
>
> 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)
