Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we handle S3 internal errors correctly? #17

Closed
henningpeters opened this issue Apr 23, 2013 · 3 comments
Closed

Do we handle S3 internal errors correctly? #17

henningpeters opened this issue Apr 23, 2013 · 3 comments
Assignees

Comments

@henningpeters
Copy link
Contributor

There is a section on internal S3 errors that should result in a retry:

http://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html

<Error>
<Code>InternalError</Code>
<Message>
We encountered an internal error. Please try again.
</Message>
<RequestId>DE9A32D1F54FC303</RequestId>
<HostId>
nU9Ukaqmsj7gfzQRH+GcnShY9xvsIiKLDY4snrcXa785napfLGHq17Ydh/MZY/Wk
</HostId>
</Error>

Are we already doing that?

@ghost ghost assigned wizzard Apr 23, 2013
@wizzard
Copy link
Member

wizzard commented Apr 23, 2013

No, we don't retry a request. currently if a request failed (response code != [200, 204, 206]) then we send error back to FUSE level.

@henningpeters
Copy link
Contributor Author

Looks like 500/503 error codes indicate a transient error and should trigger a retry, see here some discussion and further links to AWS discussion boards:

https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1590

This is happening more often than one thinks.

@wizzard
Copy link
Member

wizzard commented Aug 8, 2013

fixed.

@wizzard wizzard closed this as completed Aug 8, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants