[
https://issues.apache.org/jira/browse/FLINK-33976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811939#comment-17811939
]
David Morávek commented on FLINK-33976:
---------------------------------------
master:
92d6932ac38780e90bf9e0d659f46dd9e9b26f0e
e04a2326126bd7cfbf883baba5313914335e411f
23377711ea4615749adfb9c102e9d38978d6d7b2
5ae48935e665cf2e7dc3b1e65b2968caa40cf348
843fe8fc7e8fabebb8f9cc2daca2cdde77f555cf
e945a36de8c056fa9d12dc3e4c209da87de1391f
> 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
> Labels: pull-request-available
>
> 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)
