[
https://issues.apache.org/jira/browse/HADOOP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466799
]
Tom White commented on HADOOP-882:
----------------------------------
I was actually just writing the following response: If we throw a different
type of exception (TransientS3Exception) for recoverable error codes (there's a
complete list of error codes here BTW:
http://docs.amazonwebservices.com/AmazonS3/2006-03-01/ErrorCodeList.html) then
we can make the proxy only retry for that exception. This is in line with
HADOOP-601, but until that's done we could build an S3RetryProxy just for S3.
We still might want to follow this more general approach (if it gives us more
control), but for the time being if jets3t's retry mechanism is adequate then
let's try that.
> 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.
-
You can reply to this email to add a comment to the issue online.
