[
https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466368
]
Tom White commented on HADOOP-882:
----------------------------------
As you say, the immediate RequestTimeout after an InternalError looks like a
jets3t issue. Probably worth looking at the jets3t source or sending a message
to the jets3t list?
To implement retries, I was imagining creating a wrapper implementation of
FileSystemStore that only had retry functionality in it and delegated to
another FileSystemStore for actual storage. This would make testing easier as
well as isolating the retry code. I think the InputStreams in FileSystemStore
would need to be changed to be Files, but this should be fine.
> S3FileSystem should retry if there is a communication problem with S3
> ---------------------------------------------------------------------
>
> Key: HADOOP-882
> URL: https://issues.apache.org/jira/browse/HADOOP-882
> Project: Hadoop
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.10.1
> Reporter: Tom White
> Assigned To: Tom White
>
> File system operations currently fail if there is a communication problem
> (IOException) with S3. All operations that communicate with S3 should retry a
> fixed number of times before failing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
