You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (Jira)" <ji...@apache.org> on 2023/04/20 11:26:00 UTC

[jira] [Created] (FLINK-31866) Autoscaler metric trimming reduces the numbet of metric observations

Maximilian Michels created FLINK-31866:
------------------------------------------

             Summary: Autoscaler metric trimming reduces the numbet of metric observations
                 Key: FLINK-31866
                 URL: https://issues.apache.org/jira/browse/FLINK-31866
             Project: Flink
          Issue Type: Bug
            Reporter: Maximilian Michels
            Assignee: Maximilian Michels


The autoscaler uses a ConfigMap to store past metric observations which is used to re-initialize the autoscaler state in case of failures or upgrades.

Whenever trimming of the ConfigMap occurs, we need to make sure we also update the timestamp for the start of the metric collection, so any removed observations can be compensated with by collecting new ones. If we don't do this, the metric window will effectively shrink due to removing observations.

This can lead to triggering scaling decisions when the operator gets redeployed due to the removed items.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)