diff options
author | Jon Bratseth <bratseth@vespa.ai> | 2023-07-20 14:50:22 +0200 |
---|---|---|
committer | Jon Bratseth <bratseth@vespa.ai> | 2023-07-20 14:50:22 +0200 |
commit | 97bd65b51e942fb81eeb43b14b03cad8d2474c6d (patch) | |
tree | 3dee5ca95c3ac4380e716ba0959e09a97493a820 /config-provisioning | |
parent | 06b3744b44d2a2d4fbe18f9121af2a0c57fd9683 (diff) |
Don't scale down if we are likely to scale back up
When we decide to scale number of nodes down we'll see a lower ideal
load because we need to be able to handle one node going down.
This may lead us to be closer to ideal (at current peak load)
than otherwise anticipated, such that we are quite likely to
soon scale back up. This checks for that and avoids scaling
down dimensions where this is the case.
Diffstat (limited to 'config-provisioning')
-rw-r--r-- | config-provisioning/src/main/java/com/yahoo/config/provision/Capacity.java | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/config-provisioning/src/main/java/com/yahoo/config/provision/Capacity.java b/config-provisioning/src/main/java/com/yahoo/config/provision/Capacity.java index 735f4afd974..58b14b3b38a 100644 --- a/config-provisioning/src/main/java/com/yahoo/config/provision/Capacity.java +++ b/config-provisioning/src/main/java/com/yahoo/config/provision/Capacity.java @@ -103,7 +103,11 @@ public final class Capacity { /** Create a non-required, failable capacity request */ public static Capacity from(ClusterResources min, ClusterResources max) { - return from(min, max, IntRange.empty(), false, true, Optional.empty(), ClusterInfo.empty()); + return from(min, max, IntRange.empty()); + } + + public static Capacity from(ClusterResources min, ClusterResources max, IntRange groupSize) { + return from(min, max, groupSize, false, true, Optional.empty(), ClusterInfo.empty()); } public static Capacity from(ClusterResources resources, boolean required, boolean canFail) { |