Skip to content

A client called run_in_transaction be stuck if Spanner is down #18375

Description

@jiayun-zou

Determine this is the right repository

  • I determined this is the correct repository in which to report this bug.

Summary of the issue

Context
When the Spanner is unavailable. If we call run_in_transaction, the Spanner client will stuck forever.

We believe the get_session should in the try catch block. Otherwise, the self._local.transaction_running = True will be forever True.

Expected Behavior:
The client will retry when the Spanner DB is back.

Actual Behavior:
The client stuck forever.

API client name and version

No response

Reproduction steps: code

No response

Reproduction steps: supporting files

  • Try to create a session when Spanner is unavailable.
  • The client will be stuck forever.

Reproduction steps: actual results

No response

Reproduction steps: expected results

No response

OS & version + platform

No response

Python environment

No response

Python dependencies

No response

Additional context

No response

Activity

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