Hi,
First of all, I wish everybody a happy new year 2017. I've set user@flink in CC so that users who are interested in helping with the testing get notified. Please respond only to the dev@ list to keep the discussion there! According to the 1.2 release discussion thread, I've created a first release candidate for Flink 1.2. The release candidate will not be the final release, because I'm certain that we'll find at least one blocking issue in the candidate :) Therefore, the RC is meant as a testing only release candidate. Please report every issue we need to fix before the next RC in this thread so that we have a good overview. The release artifacts are located here: The maven staging repository is located here: The release commit (in branch "release-1.2.0-rc0"): Happy testing! |
Hi,
I downloaded the source tar ball and ran test suite. AsyncWaitOperatorTest hung: "main" #1 prio=5 os_prio=0 tid=0x00007f02c8008800 nid=0x4b8c in Object.wait() [0x00007f02cf974000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000f1b488a0> (a org.apache.flink.streaming.runtime.tasks.StreamTaskTestHarness$TaskThread) at java.lang.Thread.join(Thread.java:1253) - locked <0x00000000f1b488a0> (a org.apache.flink.streaming.runtime.tasks.StreamTaskTestHarness$TaskThread) at org.apache.flink.streaming.runtime.tasks.StreamTaskTestHarness.waitForTaskCompletion(StreamTaskTestHarness.java:208) at org.apache.flink.streaming.runtime.tasks.StreamTaskTestHarness.waitForTaskCompletion(StreamTaskTestHarness.java:193) at org.apache.flink.streaming.api.operators.async.AsyncWaitOperatorTest.testOperatorChainWithProcessingTime(AsyncWaitOperatorTest.java:378) Has anyone else seen this ? Cheers |
In reply to this post by rmetzger0
Hi, this depends a lot on the number of issues we find during the testing. These are the issues I found so far: https://issues.apache.org/jira/browse/FLINK-5379 (unresolved) https://issues.apache.org/jira/browse/FLINK-5380 (pending PR) On Tue, Jan 10, 2017 at 11:58 AM, shijinkui <[hidden email]> wrote: Do we have a probable time of 1.2 release? This month or Next month? |
I have another bugfix for 1.2.:
https://issues.apache.org/jira/browse/FLINK-2662 (pending PR) 2017-01-10 15:16 GMT+01:00 Robert Metzger <[hidden email]>: Hi, |
I also found a bunch of issues On Thu, Jan 12, 2017 at 9:56 AM, Fabian Hueske <[hidden email]> wrote: I have another bugfix for 1.2.: |
I also found an issue: I also noticed that Flink's webserver does not support https requests. It might be worthwhile to add it, though. On Thu, Jan 12, 2017 at 11:24 AM, Robert Metzger <[hidden email]> wrote: I also found a bunch of issues |
FLINK-5470 is a duplicate of FLINK-5298
for which there is also an open PR.
FLINK-5472 is imo invalid since the webserver does support https, you just have to enable it as per the security documentation. On 12.01.2017 16:20, Till Rohrmann wrote:
|
I'm wondering whether we should not depend the webserver encryption on the global encryption activation and activating it instead per default. On Thu, Jan 12, 2017 at 4:54 PM, Chesnay Schepler <[hidden email]> wrote:
|
Hi Huang, this seems to be very strange, because the JobManager’s actor system has bound to the address Could you maybe tell me which version of Flink you’re running and also share the complete JobManager log with us? I tested it with the latest 1.2 SNAPSHOT version and there it seemed to work. Cheers, On Fri, Jan 13, 2017 at 9:02 AM, huangwei (G) <[hidden email]> wrote: Dear All, |
In reply to this post by Till Rohrmann
I tested the Table API / SQL a bit. Joining a stream with a TableFunction also seemed to work well.I implemented a windowed aggregation with the streaming Table API and it produced the same results as a DataStream API implementation. Moreover, I checked the results of a bunch of TPC-H queries (batch SQL) and all produced correct results. 2017-01-12 17:45 GMT+01:00 Till Rohrmann <[hidden email]>: I'm wondering whether we should not depend the webserver encryption on the |
In reply to this post by Till Rohrmann
Hi Huang, the reason why you cannot use the IP address to send messages to your YARN JobManager is that we no longer resolve the hostname into an IP address. Instead we start the ActorSystem with the unresolved hostname. You can see this in the following log line: `Actor system bound to hostname 9-96-101-251`. Since Akka requires that the destination address of a message matches exactly the address to which the ActorSystem is bound, you have to use `9-96-101-251:38785`. This was recently changed. Concerning the ports, Flink chooses a random port for the `JobManager` in order to avoid port conflicts with other `JobManagers` running on the same node. With YARN you don't have control over where the `JobManager` is placed. However, you can use the configuration parameter `yarn.application-master.port` to specify a port or a port range for the application master/job manager. Additionally, the web frontends port is always overwritten and set to 0 which means random port selection when starting a yarn session. I hope this clarifies things a little bit. Cheers, Till On Sat, Jan 14, 2017 at 2:52 AM, huangwei (G) <[hidden email]> wrote: Hi Till, |
In reply to this post by Fabian Hueske-2
I found two problematic issues with Mesos HA mode which breaks it: On Fri, Jan 13, 2017 at 11:29 AM, Fabian Hueske <[hidden email]> wrote:
|
A user reported that outer joins on the Table API and SQL compute wrong results: https://issues.apache.org/jira/browse/FLINK-5498 2017-01-15 20:23 GMT+01:00 Till Rohrmann <[hidden email]>: I found two problematic issues with Mesos HA mode which breaks it: |
Hi all, I would like to do a proper voting RC1 early this week. From the issues mentioned here, most of them have pull requests or were changed to a lower priority. Once we've merged all outstanding PRs, I'll create the next RC. Regards, Robert On Mon, Jan 16, 2017 at 12:13 PM, Fabian Hueske <[hidden email]> wrote: A user reported that outer joins on the Table API and SQL compute wrong |
RC1 creation is in progress ... On Mon, Jan 23, 2017 at 10:33 AM, Robert Metzger <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |