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

storage- when return status 503 (backend error) auto retry. #701

Closed
leibale opened this issue Jul 5, 2015 · 6 comments
Closed

storage- when return status 503 (backend error) auto retry. #701

leibale opened this issue Jul 5, 2015 · 6 comments
Assignees
Labels
api: storage Issues related to the Cloud Storage API.

Comments

@leibale
Copy link
Contributor

leibale commented Jul 5, 2015

add option in storage (by parameter) to auto retry when google return status 503.

@leibale leibale changed the title storage- when return status 503 (backend error) try again auto after second storage- when return status 503 (backend error) auto retry. Jul 5, 2015
@stephenplusplus
Copy link
Contributor

We have a universal response handler we use on all of our requests that do this using exponential backoff, but it's possible we have some places that don't use it. Where did you notice it happening?

@leibale
Copy link
Contributor Author

leibale commented Jul 5, 2015

it's error in worker so i don't know exactly where is it, but it's or in upload image (file.createWriteStream) or in getFiles or in get file (file.createReadStream).

thanks

@stephenplusplus
Copy link
Contributor

Ok thanks for reporting. I'll check into it tomorrow.

On Sunday, July 5, 2015, leibale eidelman notifications@github.com wrote:

it's error in worker so i don't know exactly where is it, but it's or in
upload image (file.createWriteStream) or in getFiles or in get file
(file.createReadStream).

thanks


Reply to this email directly or view it on GitHub
#701 (comment)
.

@jgeewax jgeewax added the api: storage Issues related to the Cloud Storage API. label Jul 6, 2015
@stephenplusplus stephenplusplus self-assigned this Jul 6, 2015
@stephenplusplus
Copy link
Contributor

@leibale I took a shot at solving this in #705. Feel free to give it a look :)

@leibale
Copy link
Contributor Author

leibale commented Jul 6, 2015

@stephenplusplus i will try it tomorrow. thanks.

@leibale
Copy link
Contributor Author

leibale commented Jul 10, 2015

@stephenplusplus i can't try it- i need the maxInProgress option (i am using my fork)

sofisl pushed a commit that referenced this issue Nov 17, 2022
* fix: fix breaking changes in Compute API (#701)

Source-Link: googleapis/googleapis@272c110

Source-Link: googleapis/googleapis-gen@4c674ff
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNGM2NzRmZjZmZGIyYmE1OGVmY2M0ZTc5Y2RkODIyNGI2ZTA0ZGE5NCJ9

Merge branch 'owl-bot-copy' of https://github.com/googleapis/nodejs-compute into owl-bot-copy

🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

feat: update compute API to revision 20220112 (#700)

Source-Link: googleapis/googleapis@249e9a1

Source-Link: googleapis/googleapis-gen@1f2c41b
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMWYyYzQxYmJmZTA5NzYxNmNlYjFlOWZiNjc4NzJhNmJiMWRjNTlkNCJ9

* 🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* 🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API.
Projects
None yet
Development

No branches or pull requests

3 participants