fix: Use lightweight Spanner call to address memory leak #380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a memory leak affecting the Poller component, which resulted in an increasing amount of memory consumed until the Cloud Functions instance memory limit was exceeded, and the instance was terminated. The
getDatabases
call returns an array of database objects -- by using a different call to the Spanner API to retrieve the number of databases for each Spanner instance, no resources are left waiting to be freed. Fixes #376.