Re: Re: [DISCUSS] Time for 0.6.0

2025-05-13 Thread Fei Wang
Thanks for your positive feedback, I'll draft 0.6.0-rc0 soon. Thanks, Fei Wang On 2025/05/09 14:30:40 rexxiong wrote: > +1,Thanks Fei for driving this. > > Thanks, > Jiashu Xiong > > Nicholas 于2025年5月9日周五 14:44写道: > > > +1. Thanks for driving. > > > > > > Regards, > > Nicholas Jiang > > > > >

Re: [DISCUSS] CIP-17 Interruption Aware Slot Selection

2025-05-13 Thread Aravind Patnam
To add on to my answer for the 4th question -- internally we have this value to 50% given our interruption notice period is 24h. Thanks, Aravind On Tue, May 13, 2025 at 2:46 PM Aravind Patnam wrote: > Hi Nicholas, > > Thanks for the feedback and questions! Let me answer your questions below. >

Re: [DISCUSS] CIP-17 Interruption Aware Slot Selection

2025-05-13 Thread Aravind Patnam
Hi Nicholas, Thanks for the feedback and questions! Let me answer your questions below. > 1. Why is the lack of Flink replication support the motivation for disruption aware slot selection? Do you mean that disruption aware slot selection helps to reduce recompution costs for Flink without replic

Re: [DISCUSS] CIP-17 Interruption Aware Slot Selection

2025-05-13 Thread Nicholas Jiang
Hi Aravind, Thanks for driving the proposal of interruption aware slot selection. I have some comments for this proposal: 1. Why is the lack of Flink replication support the motivation for disruption aware slot selection? Do you mean that disruption aware slot selection helps to reduce recompu