The GitHub Actions job "CI" on flink-kubernetes-operator.git has succeeded.
Run started by GitHub user mxm (triggered by mxm).

Head commit for run:
c71b471fc8b0840cd8cf96cc48c41e70d795dab0 / Maximilian Michels <[email protected]>
[FLINK-30464] Exclude metrics during stabilization and ensure a full metric 
window (#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
which is fixed in this change.

Report URL: 
https://github.com/apache/flink-kubernetes-operator/actions/runs/3831689605

With regards,
GitHub Actions via GitBox

Reply via email to