HI Gordon, Thanks for bringing up the discussion. The following JIRA/PR is almost there, and it's a major/critical issue that blocks us from upgrading to Flink 1.6 or above in production. W/o this fix, a job might go into an infinite resource acquirement loop without failing itself in YARN.
FLINK-10868 <https://issues.apache.org/jira/browse/FLINK-10868>: Flink's JobCluster ResourceManager doesn't use maximum-failed-containers as limit of resource acquirement Would greatly appreciate that we could get it in for 1.7.2. Thanks a lot. Shuyi On Tue, Feb 5, 2019 at 7:32 AM Tzu-Li (Gordon) Tai <tzuli...@apache.org> wrote: > Hi Flink devs, > > What do you think about releasing Flink 1.7.2 soon? > > We already have some critical fixes in the release-1.7 branch: > - FLINK-11207: security vulnerability with currently used Apache > commons-compress version > - FLINK-11419: restore issue with StreamingFileSink > - FLINK-11436: restore issue with Flink's AvroSerializer > - FLINK-10761: potential deadlock with metrics system > - FLINK-10774: connection leak in FlinkKafkaConsumer > - FLINK-10848: problem with resource allocation in YARN mode > > Please let me know what you think. Ideally, we can kick off the release > vote for the first RC early next week. > If there are some other critical fixes for 1.7.2 that are almost completed > (already have a PR opened and review is in progress), please let me know > here by the end of the week to account for it for the 1.7.2 release. > > Cheers, > Gordon > -- "So you have to trust that the dots will somehow connect in your future."
