Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Thanks Max! Etienne Le 09/08/2023 à 12:53, Maximilian Michels a écrit : +1 (binding) -Max On Tue, Aug 8, 2023 at 10:56 AM Etienne Chauchot wrote: Hi all, As part of Flink bylaws, binding votes for FLIP changes are active committer votes. Up to now, we have only 2 binding votes. Can one

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

+1 (binding) -Max On Tue, Aug 8, 2023 at 10:56 AM Etienne Chauchot wrote: > > Hi all, > > As part of Flink bylaws, binding votes for FLIP changes are active > committer votes. > > Up to now, we have only 2 binding votes. Can one of the committers/PMC > members vote on this FLIP ? > > Thanks > >

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Hi all, As part of Flink bylaws, binding votes for FLIP changes are active committer votes. Up to now, we have only 2 binding votes. Can one of the committers/PMC members vote on this FLIP ? Thanks Etienne Le 08/08/2023 à 10:19, Etienne Chauchot a écrit : Hi Joseph, Thanks for the

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Hi Joseph, Thanks for the detailled review ! Best Etienne Le 14/07/2023 à 11:57, Prabhu Joseph a écrit : *+1 (non-binding)* Thanks for working on this. We have seen good improvement during the cool down period with this feature. Below are details on the test results from one of our

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

+1(binding) Thanks for driving this proposal, it will be useful for rescale. I’m preparing the FLIP-334[1], it will decouple the autoscaler and kubernetes. In the end, we hope all kind of flink jobs work well with rescale and autoscaler. [1]

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

+1 (binding) On Fri, Jul 14, 2023 at 11:59 AM Prabhu Joseph wrote: > *+1 (non-binding)* > > Thanks for working on this. We have seen good improvement during the cool > down period with this feature. > Below are details on the test results from one of our clusters: > > On a scale-out operation,

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

*+1 (non-binding)* Thanks for working on this. We have seen good improvement during the cool down period with this feature. Below are details on the test results from one of our clusters: On a scale-out operation, 8 new nodes were added one by one with a gap of ~30 seconds. There were 8 restarts

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Hi all, I'm going on vacation tonight for 3 weeks. Even if the vote is not finished, as the implementation is rather quick and the design discussion had settled, I preferred I implementing FLIP-322 [1] to allow people to take a look while I'm off. [1]

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Hi all, Would you mind casting your vote to this second vote thread (opened after new discussions) so that the subject can move forward ? @David, @Chesnay, @Robert you took part to the discussions, can you please sent your vote ? Thank you very much Best Etienne Le 06/07/2023 à 13:02,

[VOTE] FLIP-322 Cooldown period for adaptive scheduler. Second vote.

Hi all, Thanks for your feedback about the FLIP-322: Cooldown period for adaptive scheduler [1]. This FLIP was discussed in [2]. I'd like to start a vote for it. The vote will be open for at least 72 hours (until July 9th 15:00 GMT) unless there is an objection or insufficient votes. [1]