Hi Jincheng, +1 for a 1.8.2 release. Thanks a lot for raising the discussion. It would be nice to have these critical fixes.
Best, Hequn On Fri, Aug 30, 2019 at 6:31 PM Maximilian Michels <m...@apache.org> wrote: > Hi Jincheng, > > +1 I would be for a 1.8.2 release such that we can fix the problems with > the nested closure cleaner which currently block 1.8.1 users with Beam: > https://issues.apache.org/jira/browse/FLINK-13367 > > Thanks, > Max > > On 30.08.19 11:25, jincheng sun wrote: > > Hi Flink devs, > > > > It has been nearly 2 months since the 1.8.1 released. So, what do you > think > > about releasing Flink 1.8.2 soon? > > > > We already have some blocker and critical fixes in the release-1.8 > branch: > > > > [Blocker] > > - FLINK-13159 java.lang.ClassNotFoundException when restore job > > - FLINK-10368 'Kerberized YARN on Docker test' unstable > > - FLINK-12578 Use secure URLs for Maven repositories > > > > [Critical] > > - FLINK-12736 ResourceManager may release TM with allocated slots > > - FLINK-12889 Job keeps in FAILING state > > - FLINK-13484 ConnectedComponents end-to-end test instable with > > NoResourceAvailableException > > - FLINK-13508 CommonTestUtils#waitUntilCondition() may attempt to sleep > > with negative time > > - FLINK-13806 Metric Fetcher floods the JM log with errors when TM is > lost > > > > Furthermore, I think the following one blocker issue should be merged > > before 1.8.2 release. > > > > - FLINK-13897: OSS FS NOTICE file is placed in wrong directory > > > > It would also be great if we can have the fix of Elasticsearch6.x > connector > > threads leaking (FLINK-13689) in 1.8.2 release which is identified as > major. > > > > Please let me know what you think? > > > > Cheers, > > Jincheng > > >
