Serverles: Set size=0 for 4.15 and 4.16 cluster pools #58636
+2
−2
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 size specifies the number of hibernated clusters that wait for use. The older clusters will be rarely used from now that we have 4.17 in place.
We need at least 4 clusters for each PR so it makes sense to have the size either
0
or>=4
for old clusters. Otherwise we don't get any speed up but still need to pay for hibernated clusters.We keep the original
maxSize
so that custers can be started on demand up tomaxSize
clusters.