Skip to content

Conditionally retry HTTP calls for specific S3 errors#799

Merged
deekoder merged 1 commit into
minio:masterfrom
kannappanr:Slash_Prefix_Fix
Aug 29, 2017
Merged

Conditionally retry HTTP calls for specific S3 errors#799
deekoder merged 1 commit into
minio:masterfrom
kannappanr:Slash_Prefix_Fix

Conversation

@kannappanr
Copy link
Copy Markdown
Collaborator

@kannappanr kannappanr commented Aug 25, 2017

Fixes this issue by checking for Invalidregion related s3 error codes like

  1. InvalidRegion
  2. AuthorizationHeaderMalformed

instead of just checking for http.StatusBadRequest when the other conditions are met.
Fixes #795 and #764

Copy link
Copy Markdown
Member

@balamurugana balamurugana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@balamurugana
Copy link
Copy Markdown
Member

balamurugana commented Aug 26, 2017

Overall looks good. You could fix commit log by

Conditionally retry HTTP calls for specific S3 errors

When InvalidRegion or AuthorizationHeaderMalformed error is received from S3 server,
update bucket region cache and retry the same ReST call with returned region.

Fixes #NNN

@kannappanr kannappanr changed the title Handle slash prefixed object name properly, issue 795 Conditionally retry HTTP calls for specific S3 errors Aug 28, 2017
@kannappanr
Copy link
Copy Markdown
Collaborator Author

Fixes #795 and #764

When InvalidRegion or AuthorizationHeaderMalformed error is received from S3 server,
update bucket region cache and retry the same ReST call with returned region.

Fixes minio#795 and minio#764
@kannappanr kannappanr changed the title Conditionally retry HTTP calls for specific S3 errors Conditionally retry HTTP calls for specific S3 errors. Fixes #795 and #764 Aug 28, 2017
@kannappanr kannappanr changed the title Conditionally retry HTTP calls for specific S3 errors. Fixes #795 and #764 Conditionally retry HTTP calls for specific S3 errors Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants