[jira] [Created] (FLINK-9440) Allow cancelation and reset of timers

Elias Levy created FLINK-9440: - Summary: Allow cancelation and reset of timers Key: FLINK-9440 URL: https://issues.apache.org/jira/browse/FLINK-9440 Project: Flink Issue Type: Bug

Re: [ANNOUNCE] Apache Flink 1.5.0 release

Quick update: I had to update the date of the release blog post which also changed the URL. It can now be found here: http://flink.apache.org/news/2018/05/25/release-1.5.0.html Cheers, Till On Fri, May 25, 2018 at 7:03 PM, Hao Sun wrote: > This is great. Thanks for the

Re: [VOTE] Enable GitBox integration (#2)

+1 On Fri, May 25, 2018 at 4:14 AM, Qi Yu wrote: > +1 > > > 在 2018年5月25日，下午7:12，Till Rohrmann 写道： > > > > +1 > > > > On Wed, May 23, 2018 at 2:33 PM, Stefan Richter < > s.rich...@data-artisans.com > >> wrote: > > > >> +1 > >> > >>> Am 23.05.2018 um

[ANNOUNCE] Apache Flink 1.5.0 release

The Apache Flink community is very happy to announce the release of Apache Flink 1.5.0. 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:

[RESULT] [VOTE] Release 1.5.0, release candidate #6

I'm happy to announce that we have unanimously approved this release. There are 7 approving votes, 4 of which are binding: - Piotrek (non-binding) - Aljoscha (binding) - Timo (binding) - Tzu-Li (binding) - Till (binding) - Gary (non-binding) - Thomas (non-binding) There are no disapproving

Re: [VOTE] Release 1.5.0, release candidate #6

+1 (non-binding) - checked signatures and hashes - run Kinesis consumer test Regarding the rate of issues being found: I would credit some of it to increased coverage and due diligence and some to to the nature of changes in the release. It is probably expected that a 1.5.1 release will follow

Re: [VOTE] Release 1.5.0, release candidate #6

The voting time has passed and I'm happy to announce that we've collected enough votes to release this RC as Flink 1.5.0. +1 votes: - Piotrek (non-binding) - Aljoscha (binding) - Timo (binding) - Tzu-Li (binding) - Till (binding) - Gary (non-binding) That's 6 votes, 4 binding. No 0 or -1 votes.

Re: [VOTE] Release 1.5.0, release candidate #6

+1 (non-binding) I have tested HA capabilities on YARN (Hadoop 2.8.3). Best, Gary On Fri, May 25, 2018 at 4:54 PM, Tzu-Li (Gordon) Tai wrote: > +1 > > - Verified signatures and hashes > - Built from source with Hadoop 2.8.1 and Scala 2.11.7, tests pass locally > - No

Re: [VOTE] Release 1.5.0, release candidate #6

+1 - Verified signatures and hashes - Built from source with Hadoop 2.8.1 and Scala 2.11.7, tests pass locally - No binaries in source archives; no missing artifacts - To cover the extra Kafka connector bug fixes that were added in between RCs (FLINK-9349 and FLINK-9295), I executed Kafka

Re: [VOTE] Release 1.5.0, release candidate #6

+1 - I build the release locally with the minor issues mentioned in the last thread - I executed a couple of table programs on a local cluster - Ran some end-to-end tests locally @Piotr: Given the amount of changes that went into this release it is natural to find a lot of bugs. We have also

[PROPOSAL] Improving Flink’s timer management for large state

Hi, I am currently planning how to improve Flink’s timer management for large state. In particular, I would like to introduce timer state that is managed in RocksDB and also to improve the capabilities of the heap-based timer service, e.g. support for asynchronous checkpoints. You can find a

Re: Increasing Disk Read Throughput and IOPS

Hi, I just wanted to add that if you are using EBS you could consider to switch to IO provisioned type of it (io1: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html ) if it is ok from the cost

Re: [VOTE] Release 1.5.0, release candidate #6

+1 - verified signature and hashes - ran an example on a kerberized Hadoop 2.8.3 cluster, both with kinit and by using keytab > On 25. May 2018, at 11:56, Piotr Nowojski wrote: > > Mild +1 from me. I’m concerned about the rate of bugs that we are discovering > for

[jira] [Created] (FLINK-9439) DispatcherTest#testJobRecovery dead locks

Piotr Nowojski created FLINK-9439: - Summary: DispatcherTest#testJobRecovery dead locks Key: FLINK-9439 URL: https://issues.apache.org/jira/browse/FLINK-9439 Project: Flink Issue Type: Bug

Re: [VOTE] Enable GitBox integration (#2)

+1 On Wed, May 23, 2018 at 2:33 PM, Stefan Richter wrote: > +1 > > > Am 23.05.2018 um 14:31 schrieb Stephan Ewen : > > > > +1 > > > > On Wed, May 23, 2018 at 11:11 AM, Fabian Hueske > wrote: > > > >> +1 > >> > >> 2018-05-23

Re: Merging PR to release branches during RC voting

I second Piotr's worries concerning the merging of commits in between RCs. I think it is a good idea to create a dedicated release-x.y.z branch which is the basis for RCs for version x.y.z and that all commits being committed to this branch will go through the RM. This will make him aware of the

Re: [VOTE] Release 1.5.0, release candidate #6

Mild +1 from me. I’m concerned about the rate of bugs that we are discovering for each RC, which suggests that there are still some release blockers out there (but I’m not aware of any right now). Piotrek > On 25 May 2018, at 11:25, Till Rohrmann wrote: > > +1 > > -

Re: [VOTE] Release 1.5.0, release candidate #6

+1 - Checked checksums and GPG files - Verified that source archives do not contain any binaries - Built Flink with Hadoop 2.8.1 and Scala 2.11.7 from source release - Verified LICENSE and NOTICE file: The LICENSE file contains unnecessary entries for jline-reader and jline-terminal - Checked

Re: Flink 1.5 - Job fails to execute in multiple taskmanagers (parallelism > 1)

I just tested the workaround and it works. Thank you -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/

[jira] [Created] (FLINK-9438) Add documentation for (Registry)AvroDeserializationSchema

Dawid Wysakowicz created FLINK-9438: --- Summary: Add documentation for (Registry)AvroDeserializationSchema Key: FLINK-9438 URL: https://issues.apache.org/jira/browse/FLINK-9438 Project: Flink

Re: Flink 1.5 - Job fails to execute in multiple taskmanagers (parallelism > 1)

FYI: https://issues.apache.org/jira/browse/FLINK-9437 We will revert the changes of FLINK-9310 with Flink 1.5.1. For Flink 1.6, the problem should not arise since we are currently upgrading our Netty dependency. Cheers, Till On Fri, May 25, 2018 at 8:40 AM, Till Rohrmann

[jira] [Created] (FLINK-9437) Revert cypher suite update

Till Rohrmann created FLINK-9437: Summary: Revert cypher suite update Key: FLINK-9437 URL: https://issues.apache.org/jira/browse/FLINK-9437 Project: Flink Issue Type: Bug

Re: Increasing Disk Read Throughput and IOPS

One more thing, I am aware of one older thread that might be interesting for you about RocksDB backend and EBS: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/checkpoint-stuck-with-rocksdb-statebackend-and-s3-filesystem-td18679.html

[jira] [Created] (FLINK-9436) Remove generic parameter namespace from InternalTimeServiceManager

Stefan Richter created FLINK-9436: - Summary: Remove generic parameter namespace from InternalTimeServiceManager Key: FLINK-9436 URL: https://issues.apache.org/jira/browse/FLINK-9436 Project: Flink

Re: Increasing Disk Read Throughput and IOPS

Hi, if the problem is seemingly from reads, I think incremental checkpoints are less likely to cause the problem. What Flink version are you using? Since you mentioned the use of map state, what comes to my mind as a potential cause is described in this issue

Re: Flink 1.5 - Job fails to execute in multiple taskmanagers (parallelism > 1)

Thanks for reporting the issue Edward. Taking a look at Netty SslHandler, it looks that we introduced this problem with the update of the cipher algorithms [1]. Apparently, the SslHandler wants to use inbound heap byte buffer when using a cipher suite with GCM enabled [2]. This seems to be fixed