Cloud Spanner: creation of new database spuriously returns ALREADY_EXISTS #3
Labels
api: spanner
Issues related to the googleapis/python-spanner API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
OS type and version: standard CircleCI docker image
circleci/python:3.6.1
, running onLinux 558edcd72a3d 4.15.0-1052-aws googleapis/google-cloud-python#54-Ubuntu SMP Tue Oct 1 15:43:26 UTC 2019 x86_64 Linux
.Python version: 3.6.1
Using google-cloud-spanner library 1.13.0.
This
sampledb
integration test creates a new database, with a name including the current time down to second resolution.The test is not invoked in parallel, so this database creation should never fail due to an already existing database of the same name. However, this error did occur, as the log below shows -- maybe that's a bug in the retry implementation in the library?
It might be relevant that currently the implementation doesn't wait for the
future
returned by the database creation, which this PR will fix. So potentially that might lead to another operation to retry the creation?In the logs for the Cloud Spanner instance there is only a single error listed, for
google.spanner.admin.database.v1.DatabaseAdmin.CreateDatabase
.The text was updated successfully, but these errors were encountered: