gyfora commented on code in PR #549:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/549#discussion_r1142244157
##########
docs/layouts/shortcodes/generated/dynamic_section.html:
##########
@@ -86,6 +86,12 @@
<td>Duration</td>
<td>Interval at which periodic savepoints will be triggered. The
triggering schedule is not guaranteed, savepoints will be triggered as part of
the regular reconcile loop.</td>
</tr>
+ <tr>
+ <td><h5>kubernetes.operator.rescaling.cluster-cooldown</h5></td>
+ <td style="word-wrap: break-word;">1 min</td>
+ <td>Duration</td>
Review Comment:
I personally would not enforce any cross deployment timeout / cooldown by
default. I don't think it's intuitive why something on one deployment should
have an effect on others. Also this is specific to EKS not a general problem.
While the lack of this config may cause problems on EKS over time, it causes
immediate weird behaviour on every operator that is using the autoscaler for
multiple jobs. Imagine having 60 jobs, it will take an hour to scale once. Also
some jobs may never be scaled because there is no faire queing etc.
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
