I'm testing how ece make sure that available resource is enough for a plan and meet an interesting problem.
Let us assume that we have following available resource.
Then I want to scale one cluster to following size with 2 16GB nodes in 2 zones.
If I chose "create new" strategy, the plan quit immediately with following error.
But if I chose "rolling create new" strategy, the plan didn't quit until constructor found there were no valid allocator for all nodes.
But it ended with two new nodes like following image.
So for "rolling create new" strategy, constructor don't check the available resource for the plan like "create new" strategy. But this will bring an incomplete plan execution.
What I expect is that constructor can use the same resource capacity validation algorithm both for "create new " or "rolling create new" strategy. Because we have limited resource, so we choose "rolling create new" as the default strategy.
We hope that we can break the plan execution immediately if there is not enough capacity.