- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2026 04:54 PM
Hello,
I have a theoretical question for which I have not been able to find a clear answer in the documentation.
When a cluster is created using an instance pool, what exactly is checked when the pool is asked to provide nodes?
More specifically, does the pool check whether:
the maximum number of nodes configured for the new cluster is less than or equal to the number of nodes currently available in the pool (idle or not),
or whether:
the maximum number of nodes configured for the new cluster is less than or equal to the number of nodes available in the pool (idle or not), after also accounting for the remaining capacity that could still be allocated to existing clusters already using the pool but not yet at their maximum size?
For example, let’s say we have a pool with a maximum capacity of 23 nodes.
A first cluster is created with 6 nodes and a maximum of 12 nodes. The pool accepts the request and provides the initial 6 nodes.
Then a second cluster, also configured with 6 nodes and a maximum of 12 nodes, is created.
Would the pool accept the second cluster because 23 - 6 = 17, which is still greater than 12?
Or would it reject it because 23 - 12 = 11, which is less than 12, meaning the first cluster’s unused scaling capacity is already effectively reserved?
Thank you in advance for your clarification.
- Labels:
-
Workflows