fix: never try to create a negative number of sessions #1467
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.
The session pool should never try to create a negative number of sessions. Especially the
_fillmethod could try that, as it would createthis.options.min! - this.sizesessions. That works well for an empty session pool, but not for one that has already been filled, and can cause the_pendingvalue to become negative.It might be that the
_fillmethod could cause the strange statistics that we see in #1465 if the following happens:_fillis called after the session pool has been initialized (i.e. there is at least 1 session in the pool)_pendingis increased with a negative number, potentially causing it to become negative:nodejs-spanner/src/session-pool.ts
Line 827 in b193122
_pendingis never updated when the sessions are created or the creation fails.Updates #1465