Re: [VOTE] Release 1.10.0, release candidate #3

Hi, @Jingsong Lee Regarding "OutOfMemoryError: Direct buffer memory" in FileChannelBoundedData$FileBufferReader I saw you created a specific issue issue: https://issues.apache.org/jira/browse/FLINK-15981 In general, I think we could rewrap this error in

[RESULT] [VOTE] Release 1.10.0, release candidate #3

I'm happy to announce that we have unanimously approved this release. There are 16 approving votes, 5 of which are binding: * Kurt Young (binding) * Jark Wu (binding) * Kostas Kloudas (binding) * Thomas Weise (binding) * Jincheng Sun (binding) * Aihua Li (non-binding) * Zhu Zhu (non-binding) *

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) - Build from source - Run mesos e2e tests(including unmerged heap state backend and rocks state backend case) Best, Yangze Guo On Tue, Feb 11, 2020 at 10:08 AM Yu Li wrote: > > Thanks for the reminder Patrick! According to the release process [1] we > will publish the

Re: [VOTE] Release 1.10.0, release candidate #3

Thanks for the reminder Patrick! According to the release process [1] we will publish the Dockerfiles *after* the RC voting passed, to finalize the release. I have created FLINK-15978 [2] and prepared a PR [3] for it, will follow up after we conclude our RC vote. Thanks. Best Regards, Yu [1]

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (binding) - Download the source code [SUCCESS] - Build the source release with Scala 2.12 and Scala 2.11 [SUCCESS] - Checked/verified signatures and hashes [SUCCESS] - Pip install PyFlink by `pip3 install apache-flink-1.10.0.tar.gz` [SUCCESS] - Run a word_count.py both in command line and

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) - source doesn't contain binary files & build from source - run against stability test cases - manually verify YARN CLI & deployment work as expected Best, tison. Thomas Weise 于2020年2月11日周二 上午2:48写道： > +1 (binding) > > - verified signatures and hashes > - rebased internal

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (binding) - verified signatures and hashes - rebased internal deploy to rc3 and verified that previously reported issues are resolved Thank you for addressing these issues promptly! Thomas On Fri, Feb 7, 2020 at 1:54 PM Gary Yao wrote: > Hi everyone, > Please review and vote on the

Re: [VOTE] Release 1.10.0, release candidate #3

Hi all, +1 (binding) - Built Flink locally - Tested quickstart by writing simple, WordCount-like streaming jobs - Submitted them to Yarn both "per-job" and "session" mode - used the yarn-session CLI to start/stop sessions Thanks a lot Gary and Yu for managing the release. Cheers, Kostas On

Re: [VOTE] Release 1.10.0, release candidate #3

Now that [FLINK-15828] Integrate docker-flink/docker-flink into Flink release process is complete, the Dockerfiles for 1.10.0 can be published as part of the release process. @Gary/@Yu: please let me know if you have any questions regarding the

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) - build from source - start standalone cluster, and run some examples - played with sql-client with some simple sql - run tests in IDE - run some sqls running in 1.9 internal version with 1.10.0-rc3, seems 1.10 behaves well. Xintong Song 于2020年2月10日周一 下午8:13写道： > +1

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) - build from source (with tests) - run nightly e2e tests - run example jobs in local/standalone/yarn setups - play around with memory configurations on local/standalone/yarn setups Thank you~ Xintong Song On Mon, Feb 10, 2020 at 7:55 PM Jark Wu wrote: > +1 (binding) > > -

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (binding) - build the source release with Scala 2.12 and Scala 2.11 successfully - checked/verified signatures and hashes - started cluster for both Scala 2.11 and 2.12, ran examples, verified web ui and log output, nothing unexpected - started cluster and run some e2e sql queries, all of them

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (binding) - verified signatures and checksums - start local cluster, run some examples, randomly play some sql with sql client, no suspicious error/warn log found in log files - repeat above operation with both scala 2.11 and 2.12 binary Best, Kurt On Mon, Feb 10, 2020 at 6:38 PM Yang Wang

Re: [VOTE] Release 1.10.0, release candidate #3

+1 non-binding I’ve re-done the manual EMR tests, including running some examples. Piotrek > On 10 Feb 2020, at 11:37, Yang Wang wrote: > > +1 non-binding > > > - Building from source with all tests skipped > - Build a custom image with 1.10-rc3 > - K8s tests >* Deploy a standalone

Re: [VOTE] Release 1.10.0, release candidate #3

+1 non-binding - Building from source with all tests skipped - Build a custom image with 1.10-rc3 - K8s tests * Deploy a standalone session cluster on K8s and submit multiple jobs * Deploy a standalone per-job cluster * Deploy a native session cluster on K8s with/without HA

Re: [VOTE] Release 1.10.0, release candidate #3

Hi, +1 (non-binding) Thanks for driving this, Gary & Yu. There is an unfriendly error here: "OutOfMemoryError: Direct buffer memory" in FileChannelBoundedData$FileBufferReader. It forces our batch users to configure "taskmanager.memory.task.off-heap.size" in production jobs. And users are

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) for rc3 - Built from source (release tag) - Downloaded binaries and verified Hive catalog/connector by manually running some queries against Hive tables On Mon, Feb 10, 2020 at 2:28 PM Congxian Qiu wrote: > +1 (non-binding) for rc3 > > - build source successfully

Re: [VOTE] Release 1.10.0, release candidate #3

+1 (non-binding) for rc3 - build source successfully (inlcude test) - ran e2e test locally - test pojo serializer upgrade manually by running flink job. Best, Congxian Zhu Zhu 于2020年2月10日周一 下午12:28写道： > My bad. The missing commit info is caused by building from the src code zip > which does

Re: [VOTE] Release 1.10.0, release candidate #3

My bad. The missing commit info is caused by building from the src code zip which does not contain the git info. So this is not a problem. +1 (binding) for rc3 Here's what's were verified : * built successfully from the source code * run a sample streaming and a batch job with parallelism=1000

Re: [VOTE] Release 1.10.0, release candidate #3

The commit info is shown as on the web UI and in logs. Not sure if it's a common issue or just happens to my build only. Thanks, Zhu Zhu aihua li 于2020年2月9日周日 下午7:42写道： > Yes, but the results you see in the Performance Code Speed Center [3] skip > FLIP-49. > The results of the default

Re: [VOTE] Release 1.10.0, release candidate #3

Yes, but the results you see in the Performance Code Speed Center [3] skip FLIP-49. The results of the default configurations are overwritten by the latest results. > 2020年2月9日 下午5:29，Yu Li 写道： > > Thanks for the efforts Aihua! These could definitely improve our RC test > coverage! > >

Re: [VOTE] Release 1.10.0, release candidate #3

Thanks for the efforts Aihua! These could definitely improve our RC test coverage! Just to confirm, that the stability tests were executed with the same test suite for Alibaba production usage, and the e2e performance one was executed with the test suite proposed in FLIP-83 [1] and FLINK-14917

[VOTE] Release 1.10.0, release candidate #3

Hi everyone, Please review and vote on the release candidate #3 for the version 1.10.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * JIRA release notes [1],