Fly-Style commented on code in PR #19269:
URL: https://github.com/apache/druid/pull/19269#discussion_r3062185886


##########
indexing-service/src/main/java/org/apache/druid/indexing/seekablestream/supervisor/autoscaler/CostBasedAutoScaler.java:
##########
@@ -174,11 +174,26 @@ public int computeTaskCountForScaleAction()
     lastKnownMetrics = collectMetrics();
 
     final int optimalTaskCount = computeOptimalTaskCount(lastKnownMetrics);
-    final int currentTaskCount = supervisor.getIoConfig().getTaskCount();
+    int currentTaskCount = supervisor.getIoConfig().getTaskCount();
+
+    // Take the current task count but clamp it to the configured boundaries 
if it is outside the boundaries.
+    // There might be a configuration instance with a handwritten taskCount 
that is outside the boundaries.
+    final boolean isTaskCountOutOfBounds = currentTaskCount < 
config.getTaskCountMin()
+                                     || currentTaskCount > 
config.getTaskCountMax();
+    if (isTaskCountOutOfBounds) {
+      currentTaskCount = Math.min(config.getTaskCountMax(),
+                                   Math.max(config.getTaskCountMin(), 
supervisor.getIoConfig().getTaskCount()));
+    }
 
     // Perform scale-up actions; scale-down actions only if configured.
     final int taskCount;
-    if (isScaleActionAllowed() && optimalTaskCount > currentTaskCount) {
+
+    // If task count is out of bounds, scale to the configured boundary
+    // regardless of optimal task count, to get back to a safe state.
+    if (isScaleActionAllowed() && isTaskCountOutOfBounds) {

Review Comment:
   That's a tricky thing, but my take here is -- eventually we will scale (and 
by eventually I mean - within  `minTriggerScaleActionFrequencyMillis` ms), and 
it _might be_ harmful to scale immediately.
   
   I don't have a strong opinion here, I am open to remove 
`isScaleActionAllowed()` from the condition.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to