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

Recognize and handle 'Instance not found' #60

Closed
olavloite opened this issue Feb 5, 2020 · 0 comments · Fixed by #61
Closed

Recognize and handle 'Instance not found' #60

olavloite opened this issue Feb 5, 2020 · 0 comments · Fixed by #61
Assignees
Labels
api: spanner priority: p2 type: bug

Comments

@olavloite
Copy link
Contributor

@olavloite olavloite commented Feb 5, 2020

The client library recognizes DatabaseNotFound errors and handles these by halting any further RPCs for the database, as the RPCs would fail. This should also be done for InstanceNotFound.

@olavloite olavloite added priority: p2 type: bug labels Feb 5, 2020
@olavloite olavloite self-assigned this Feb 5, 2020
@product-auto-label product-auto-label bot added the api: spanner label Feb 5, 2020
olavloite added a commit that referenced this issue Feb 5, 2020
The session pool should handle InstanceNotFound in the same way
as DatabaseNotFound errors, i.e. stop sending RPCs and also
consider an instance that has been re-created with the same name
as a different instance, and hence require the user to re-create
any database client before it can be used again.

Fixes #60
skuruppu pushed a commit that referenced this issue Feb 6, 2020
The session pool should handle InstanceNotFound in the same way
as DatabaseNotFound errors, i.e. stop sending RPCs and also
consider an instance that has been re-created with the same name
as a different instance, and hence require the user to re-create
any database client before it can be used again.

Fixes #60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner priority: p2 type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant