Reading from a non-existent database causes memory usage to grow #1089
Labels
api: spanner
Issues related to the googleapis/java-spanner API.
triage me
I really want to be triaged.
It seems like requests that fail with a NOT_FOUND error can cause the Spanner client to consume memory. I suspect that it is caused by the invalidatedDbClients field in SpannerImpl:
java-spanner/google-cloud-spanner/src/main/java/com/google/cloud/spanner/SpannerImpl.java
Line 96 in 71d7fd1
I ran this test program to reproduce the issue with Java 11 and google-cloud-spanner 6.3.2:
The text was updated successfully, but these errors were encountered: