Forwarding my concern from the previous RC thread: https://issues.apache.org/jira/browse/FLINK-6646 might be a blocker, because it voids Flink's HA capabilities.
Robert argued that this is not a blocker because it was already broken in 1.2 and users didn't complain about it. Therefore, it seems to affect only corner cases. I think that partial high-availability is as good as no high-availability at all. Therefore, I think we should cancel this RC and create a new one containing a fix for the problem. Moreover, this is not only a problem of the session mode but also for the per job cluster mode. Users simply didn't run into the problem, because apparently their JM recovery didn't take longer than 60s. Cheers, Till On Wed, May 24, 2017 at 6:25 PM, Robert Metzger <rmetz...@apache.org> wrote: > Hi all, > > this is the first VOTEing release candidate for Flink 1.3.0 > > The commit to be voted on: > e0a886e9 <http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e9> > (*http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e9 > <http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e9>*) > > Branch: > release-1.3.0-rc2 > > The release artifacts to be voted on can be found at: > *http://people.apache.org/~rmetzger/flink-1.3.0-rc2/ > <http://people.apache.org/~rmetzger/flink-1.3.0-rc2/>* > > The release artifacts are signed with the key with fingerprint D9839159: > http://www.apache.org/dist/flink/KEYS > > The staging repository for this release can be found at: > *https://repository.apache.org/content/repositories/orgapacheflink-1121 > <https://repository.apache.org/content/repositories/orgapacheflink-1121>* > > ------------------------------------------------------------- > > > The vote ends on Monday (May 29th), 7pm CET. > > [ ] +1 Release this package as Apache Flink 1.3.0 > [ ] -1 Do not release this package, because ... >
