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

Posted to issues@flink.apache.org by "David Morávek (Jira)" <ji...@apache.org> on 2024/01/03 12:18:00 UTC

[jira] [Assigned] (FLINK-33976) AdaptiveScheduler cooldown period is taken from a wrong configuration

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

David Morávek reassigned FLINK-33976:
-------------------------------------

    Assignee: David Morávek

> AdaptiveScheduler cooldown period is taken from a wrong configuration
> ---------------------------------------------------------------------
>
>                 Key: FLINK-33976
>                 URL: https://issues.apache.org/jira/browse/FLINK-33976
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Configuration, Runtime / Coordination
>            Reporter: David Morávek
>            Assignee: David Morávek
>            Priority: Major
>
> The new JobManager options introduced in FLINK-21883: `scaling-interval.\{min,max}` of AdaptiveScheduler are resolved from the per-Job configuration instead of JobManager's configuration, which is not correct.



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