Skip to content
This repository was archived by the owner on Feb 23, 2026. It is now read-only.

ServiceUnavailable missing in polling retries #183

Closed

Description

@hoonji

"503 service unavailable" errors are not being retried when long running operations (e.g. dataproc create_cluster) are polled.

Currently, the default retry predicate (retry.py) includes google.api_core.exceptions.ServiceUnavailable, but the polling retry predicate (polling.py) overrides the former and doesn't include ServiceUnavailable. This doesn't look intentional: if retry.py considers ServiceUnavailable to be transient and retriable, so should polling.py.

This is causing issues for customers: e.g. their Cloud Function crashes during polling when they encounter a single connection reset.

Activity

  1. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    and removed
    triage meI really want to be triaged.
    on May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions