gyfora commented on code in PR #493:
URL: 
https://github.com/apache/flink-kubernetes-operator/pull/493#discussion_r1057663391


##########
flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/autoscaler/ScalingMetricCollector.java:
##########
@@ -122,7 +130,15 @@ public CollectedMetrics getMetricsHistory(
 
         // Add scaling metrics to history if they were computed successfully
         scalingMetricHistory.put(clock.instant(), scalingMetrics);
-        scalingInformation.updateMetricHistory(currentJobStartTs, 
scalingMetricHistory);
+        scalingInformation.updateMetricHistory(currentJobUpdateTs, 
scalingMetricHistory);
+
+        if (currentJobUpdateTs
+                .plus(stabilizationDuration)
+                .isAfter(clock.instant().minus(metricsWindowDuration))) {

Review Comment:
   I think the min/max is actually simpler to understand and configure . If 
oscillation occurs then your stabilization period may be too small?
   
   the default for min/max could be the same duration but I would not make this 
more complicated 



-- 
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]

Reply via email to