Thanks for all of your feedback! Hi Yang, great thanks for working on FLINK-13184 and advancing this issue, we hope that more problems can be solved in 1.8.3.
Hi Hequn, glad to hear that you want to be the Release Manager of flink 1.8.3. I believe that you will be a great RM, and I am very willing to help you with the final release in the final stages. :) The release of Apache Flink involves a number of tasks. For details, you can consult the documentation [1]. If you have any questions, please let me know and let us work together. [1] https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release Best, Jincheng Yang Wang <danrtsey...@gmail.com> 于2019年11月10日周日 下午8:09写道: > Hi Jincheng, Hequn > > I am now working on FLINK-13184 and already attach a PR to fix this issue. > I think it is > important for large scale deployment on yarn(1000+ containers). It > will accelerate TaskExecutor > launch and reduce the pressure of hdfs. I hope it could be merge to 1.8.3. > > > Best, > Yang > > Yu Li <car...@gmail.com> 于2019年11月10日周日 上午10:58写道: > > > +1 for starting the 1.8.3 release cycle. Thanks for watching and driving > > this forward jincheng! > > > > Also +1 for Hequn to be the 1.8.3 RM. > > > > Best Regards, > > Yu > > > > > > On Sat, 9 Nov 2019 at 23:36, Jark Wu <imj...@gmail.com> wrote: > > > > > +1 for the 1.8.3 release and for Hequn being the RM. > > > Thanks Jincheng for the effort and help on the releasing. > > > > > > Best, > > > Jark > > > > > > > > > > > > On Sat, 9 Nov 2019 at 15:59, Hequn Cheng <chenghe...@gmail.com> wrote: > > > > > > > Hi Jincheng, > > > > > > > > Thanks for kicking this discussion off! > > > > > > > > +1 to the 1.8.3 release as it would be nice to have these important > > fixes > > > > and also two > > > > months have passed since the last release. > > > > > > > > Besides, I wonder if I can be the release manager of 1.8.3 or work > with > > > you > > > > together @Jincheng? > > > > It's always exciting to help the community as much as possible. > > > > > > > > Best, Hequn > > > > > > > > On Sat, Nov 9, 2019 at 12:34 PM Dian Fu <dian0511...@gmail.com> > wrote: > > > > > > > > > Hi Jincheng, > > > > > > > > > > Thanks a lot for bringing up this discussion. +1 for releasing > 1.8.3. > > > > > > > > > > Regards, > > > > > Dian > > > > > > > > > > On Sat, Nov 9, 2019 at 12:11 PM jincheng sun < > > sunjincheng...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hi Flink devs, > > > > > > > > > > > > It has been more than 2 months since the 1.8.2 released. So, What > > do > > > > you > > > > > > think about releasing Flink 1.8.3 soon? > > > > > > > > > > > > We already have many important bug fixes in the release-1.8 > branch > > > (29 > > > > > > resolved issues). > > > > > > > > > > > > Most notable fixes are: > > > > > > > > > > > > - FLINK-14010 Dispatcher & JobManagers don't give up leadership > > when > > > AM > > > > > is > > > > > > shut down > > > > > > - FLINK-14315 NPE with JobMaster.disconnectTaskManager > > > > > > - FLINK-12848 Method equals() in RowTypeInfo should consider > > > > fieldsNames > > > > > > - FLINK-12342 Yarn Resource Manager Acquires Too Many Containers > > > > > > - FLINK-14589 Redundant slot requests with the same AllocationID > > > leads > > > > to > > > > > > inconsistent slot table > > > > > > > > > > > > Furthermore, the following critical issues is in progress, maybe > we > > > can > > > > > > wait for it if it is not too much effort. > > > > > > > > > > > > - FLINK-13184 Starting a TaskExecutor blocks the > > > YarnResourceManager's > > > > > main > > > > > > thread > > > > > > > > > > > > Please let me know what you think? > > > > > > > > > > > > Best, > > > > > > Jincheng > > > > > > > > > > > > > > > > > > > > >