Skip to content

storage: Add exponential backoff for REFUSED_STREAM errors #701

@lhecker

Description

@lhecker

We're currently facing issues with GCS in production returning REFUSED_STREAM errors sporadically.
Would it be feasible to add the already existing exponential backoff logic (on 5xx and 429 errors) to REFUSED_STREAM errors as well?
It's currently in discussion for Go to add official support for this in golang/go#20985, but until then it'd be awesome if the Google Cloud client libraries could already implement this manually.

What do you think? 🙂

Metadata

Metadata

Assignees

Labels

api: storageIssues related to the Cloud Storage API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions