mxm commented on PR #711: URL: https://github.com/apache/flink-kubernetes-operator/pull/711#issuecomment-1819233149
What you describe is already the case. Any deployment which currently takes longer than the configured rescale time, will not scale accurately. By adding the feature in its current state, we are conservatively addressing those deployment which come back up much quicker. In our environment, typical rescale time is 1 minute or less. I think your request requires adding a new configuration `MAX_RESTART_TIME` because we want to (1) have a good default when we haven't yet estimated the rescale time (e.g. first scaling) via the existing setting, and (2) cap the determined rescale time for safety reasons (e.g. unexpected cluster downtime). -- 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]
