You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2023/11/15 12:42:00 UTC

[jira] [Updated] (FLINK-32960) Logic to log vertex exclusion only once does not work correctly

     [ https://issues.apache.org/jira/browse/FLINK-32960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora updated FLINK-32960:
-------------------------------
    Fix Version/s: kubernetes-operator-1.8.0
                       (was: kubernetes-operator-1.7.0)

> Logic to log vertex exclusion only once does not work correctly
> ---------------------------------------------------------------
>
>                 Key: FLINK-32960
>                 URL: https://issues.apache.org/jira/browse/FLINK-32960
>             Project: Flink
>          Issue Type: Bug
>          Components: Autoscaler, Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.6.0
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>             Fix For: kubernetes-operator-1.8.0
>
>
> As part of daeb4b6559f0d26b1b0f23be5e8230f895b0a03e we wanted to log vertex exclusion only once. This logic does not work because the vertices without busy time are excluded in memory for every run. So we print "No busyTimeMsPerSecond metric available for {}. No scaling will be performed for this vertex." for every run.



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