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

feat: Add retry support for 504 (Gateway Timeout) #704

Merged
merged 1 commit into from
Nov 1, 2021

Conversation

danielbankhead
Copy link
Contributor

Fixes a downstream issue googleapis/nodejs-storage#1635 by adding support for gateway timeouts - which is also compliant with https://cloud.google.com/storage/docs/retry-strategy#idempotency-operations

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes googleapis/nodejs-storage#1635 🦕

@danielbankhead danielbankhead requested a review from a team as a code owner November 1, 2021 02:28
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Nov 1, 2021
@danielbankhead danielbankhead added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Nov 1, 2021
@danielbankhead
Copy link
Contributor Author

Added labels/do not merge as this may be a breaking change for downstream customers (need to investigate)

Copy link
Contributor

@JustinBeckwith JustinBeckwith left a comment

Choose a reason for hiding this comment

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

From a breaking change perspective, I think this is fine and won't harm anything. From a practical standpoint though, we need to make 100% sure GCS isn't the cause of these responses. It's very likely a users upstream proxy causing the problem, and there's only so much dancing around that we can really do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add retry logic to file.download because it fails with 504 often
3 participants