Hi, Etienne. Thanks for driving it. I have one question about the mechanism of the cooldown timeout.
>From the Proposed Changes part, if a scalling event is received and it falls >during the cooldown period, it'll be stacked to be executed after the period >ends. Also, from the description of FLINK-21883[1], cooldown timeout is to avoid rescaling the job very frequently, because TaskManagers are not all connecting at the same time. So, is it possible that every taskmanager connecting will produce a scalling event and it'll be stacked with many scale up event which causes it'll take a long time to finish all? Can we just take the last one event? [1]: https://issues.apache.org/jira/browse/FLINK-21883 Best regards, Yuxia ----- 原始邮件 ----- 发件人: "Etienne Chauchot" <echauc...@apache.org> 收件人: "dev" <dev@flink.apache.org>, "Robert Metzger" <metrob...@gmail.com> 发送时间: 星期一, 2023年 6 月 12日 下午 11:34:25 主题: [DISCUSS] FLIP-322 Cooldown period for adaptive scheduler Hi, I’d like to start a discussion about FLIP-322 [1] which introduces a cooldown period for the adaptive scheduler. I'd like to get your feedback especially @Robert as you opened the related ticket and worked on the reactive mode a lot. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-322+Cooldown+period+for+adaptive+scheduler Best Etienne
