Hi Thomas Weise We have an issue related to this problem https://issues.apache.org/jira/browse/FLINK-14147, but I think you could open another JIRA The watermark data comes from metric REST API, which is too heavy for high parallelism jobs, the API almost sure will break when the parallelism is too high We could hide the error message as a temp solution and refactor the API to solve this issue completely later.
Thomas Weise <t...@apache.org> 于2019年10月21日周一 上午1:31写道： > Thanks Jark and everyone who contributed to the release! > > I took 1.9.1 for a test drive, upgrading an existing 1.8.x deployment. This > brought in the shiny new UI :) > > Everything looks good so far, except an error message that is flickering on > the job overview page: "Server response message: unable to load requested > file.." > > Looking at what is being requested makes me gasp.. > > > 1. > > http://somehost/jobs/047082c3386e250a1e0607360a003022/vertices/5995a65cc0e8d66f0ffa0d05c183c8f8/metrics?get=0.currentInputWatermark,1.currentInputWatermark,2.currentInputWatermark,3.currentInputWatermark,4.currentInputWatermark,5.currentInputWatermark,6.currentInputWatermark,7.currentInputWatermark,8.currentInputWatermark,9.currentInputWatermark,10.currentInputWatermark,11.currentInputWatermark,12.currentInputWatermark,13.currentInputWatermark,14.currentInputWatermark,15.currentInputWatermark,16.currentInputWatermark,17.currentInputWatermark,18.currentInputWatermark,19.currentInputWatermark,20.currentInputWatermark,21.currentInputWatermark,22.currentInputWatermark,23.currentInputWatermark,24.currentInputWatermark,25.currentInputWatermark,26.currentInputWatermark,27.currentInputWatermark,28.currentInputWatermark,29.currentInputWatermark,30.currentInputWatermark, > <CUT > LOT OF STUFF>,255.currentInputWatermark > 2. > > This just won't work for high parallelism jobs. The watermark display was > already broken with the old UI, thankfully now it's a bit more obvious. Is > this a known/previously reported issue for 1.9.x? > > Thanks, > Thomas > > > On Sat, Oct 19, 2019 at 6:24 PM Hequn Cheng <chenghe...@gmail.com> wrote: > > > Thanks a lot to Jark, Jincheng, and everyone that make this release > > possible. > > > > Best, Hequn > > > > On Sat, Oct 19, 2019 at 10:29 PM Zili Chen <wander4...@gmail.com> wrote: > > > > > Thanks a lot for being release manager Jark. Great work! > > > > > > Best, > > > tison. > > > > > > > > > Till Rohrmann <trohrm...@apache.org> 于2019年10月19日周六 下午10:15写道： > > > > > >> Thanks a lot for being our release manager Jark and thanks to everyone > > >> who has helped to make this release possible. > > >> > > >> Cheers, > > >> Till > > >> > > >> On Sat, Oct 19, 2019 at 3:26 PM Jark Wu <imj...@gmail.com> wrote: > > >> > > >>> Hi, > > >>> > > >>> The Apache Flink community is very happy to announce the release of > > >>> Apache Flink 1.9.1, which is the first bugfix release for the Apache > > Flink > > >>> 1.9 series. > > >>> > > >>> Apache Flink® is an open-source stream processing framework for > > >>> distributed, high-performing, always-available, and accurate data > > streaming > > >>> applications. > > >>> > > >>> The release is available for download at: > > >>> https://flink.apache.org/downloads.html > > >>> > > >>> Please check out the release blog post for an overview of the > > >>> improvements for this bugfix release: > > >>> https://flink.apache.org/news/2019/10/18/release-1.9.1.html > > >>> > > >>> The full release notes are available in Jira: > > >>> https://issues.apache.org/jira/projects/FLINK/versions/12346003 > > >>> > > >>> We would like to thank all contributors of the Apache Flink community > > >>> who helped to verify this release and made this release possible! > > >>> Great thanks to @Jincheng for helping finalize this release. > > >>> > > >>> Regards, > > >>> Jark Wu > > >>> > > >> > > >
