mxm opened a new pull request, #493: URL: https://github.com/apache/flink-kubernetes-operator/pull/493
So far, the code collects metrics as soon as the job goes into RUNNING mode, regardless of whether we are still in the stabilization period. This means the first metric collection window after rescaling will include metrics from the stabilization period. This is not desirable. The stabilization period is supposed to allow the job to stabilize. Metrics during stabilization shouldn't be used to make new scaling decisions. Further, the collected metrics for the scaling decider initially do not span a full metric window. Only after the first metric window is complete, we are guaranteed to have a full windows available. This leads to short-sighted scaling decisions. -- 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]
