[jira] [Created] (FLINK-6472) BoundedOutOfOrdernessTimestampExtractor does not bound out of orderliness
Elias Levy created FLINK-6472: - Summary: BoundedOutOfOrdernessTimestampExtractor does not bound out of orderliness Key: FLINK-6472 URL: https://issues.apache.org/jira/browse/FLINK-6472 Project: Flink Issue Type: Bug Components: Streaming Affects Versions: 1.3.0 Reporter: Elias Levy {{BoundedOutOfOrdernessTimestampExtractor}} attempts to emit watermarks that lag behind the largest observed timestamp by a configurable time delta. It fails to so in some circumstances. The class extends {{AssignerWithPeriodicWatermarks}}, which generates watermarks in periodic intervals. The timer for this intervals is a processing time timer. In circumstances where there is a rush of events (restarting Flink, unpausing an upstream producer, loading events from a file, etc), many events with timestamps much larger that what the configured bound would normally allow will be sent downstream without a watermark. This can have negative effects downstream, as operators may be buffering the events waiting for a watermark to process them, thus leading the memory growth and possible out-of-memory conditions. It is probably best to have a bounded out of orderliness extractor that is based on the punctuated timestamp extractor, so we can ensure that watermarks are generated in a timely fashion in event time, with the addition of process time timer to generate a watermark if there has been a lull in events, thus also bounding the delay of generating a watermark in processing time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FLINK-6471) RocksDBStateBackendTest#testCancelRunningSnapshot fails
Ted Yu created FLINK-6471: - Summary: RocksDBStateBackendTest#testCancelRunningSnapshot fails Key: FLINK-6471 URL: https://issues.apache.org/jira/browse/FLINK-6471 Project: Flink Issue Type: Test Reporter: Ted Yu Priority: Minor I got the following test failure based on commit f37988c19adc30d324cde83c54f2fa5d36efb9e7 : {code} testCancelRunningSnapshot[1](org.apache.flink.contrib.streaming.state.RocksDBStateBackendTest) Time elapsed: 0.166 sec <<< FAILURE! java.lang.AssertionError: null at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.apache.flink.contrib.streaming.state.RocksDBStateBackendTest.testCancelRunningSnapshot(RocksDBStateBackendTest.java:313) Results : Failed tests: RocksDBStateBackendTest.testCancelRunningSnapshot:313 null {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [外部邮件] Re: [外部邮件] Re: [外部邮件] Re: request contributor permissions
Hi, done. Welcome to the Flink community! Best, Fabian 2017-05-06 2:53 GMT+02:00 vino yang: > Hi, > Please give me contributor permissions. My JIRA username is: yanghua . > > Thanks! > > 2017-05-05 17:43 GMT+08:00 Till Rohrmann : > > > Alright, I've given you contributor rights. Welcome to the Flink > community > > :-) > > > > On Fri, May 5, 2017 at 11:15 AM, 郭健 wrote: > > > > > Yes, this is my another email. > > > > > > 在 17/5/5 16:12,“Till Rohrmann” 写入: > > > > > > Hi, > > > > > > Aegeaner seems to be associated with westla...@126.com. Is that > also > > > your > > > email address? > > > > > > Cheers, > > > Till > > > > > > On Fri, May 5, 2017 at 8:37 AM, 郭健 wrote: > > > > > > > Any one could give me contributor permission please? > > > > JIRA username: Aegeaner > > > > Email: xih...@gmail.com > > > > > > > > 在 17/5/4 15:48,“郭健” 写入: > > > > > > > > Request for contributor permission too, my jira username is : > > > Aegeaner > > > > Thanks > > > > > > > > 在 17/5/3 23:57,“Till Rohrmann” 写入: > > > > > > > > Hi, > > > > > > > > you should now have contributor rights. > > > > > > > > Cheers, > > > > Till > > > > > > > > On Wed, May 3, 2017 at 5:42 PM, 杨华 < > yanghua1...@gmail.com> > > > wrote: > > > > > > > > > Hi guys: > > > > > > > > > > Could somebody give me contributor permissions? my jira > > > username > > > > is : > > > > > yanghua. > > > > > > > > > > Thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
[jira] [Created] (FLINK-6469) Configure Memory Sizes via units
Stephan Ewen created FLINK-6469: --- Summary: Configure Memory Sizes via units Key: FLINK-6469 URL: https://issues.apache.org/jira/browse/FLINK-6469 Project: Flink Issue Type: Improvement Components: Core Reporter: Stephan Ewen Currently, memory sizes are configured by pure numbers, the interpretation is different from configuration parameter to parameter. For example, heap sizes are configured in megabytes, network buffer memory is configured in bytes, alignment thresholds are configured in bytes. I propose to configure all memory parameters the same way, with units similar to time. The JVM itself configured heap size similarly: {{Xmx5g}} or {{Xmx2000m}}. {code} 1 -> bytes 10 kb 64 mb 1 gb ... {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (FLINK-6468) release 1.2.1 tag in git
Petr Novotnik created FLINK-6468: Summary: release 1.2.1 tag in git Key: FLINK-6468 URL: https://issues.apache.org/jira/browse/FLINK-6468 Project: Flink Issue Type: Bug Components: Build System Affects Versions: 1.2.1 Reporter: Petr Novotnik Priority: Minor It appears that the `release-1.2.1` tag in missing in the git repository. It would be great to have it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [DISCUSS] Feature Freeze
I merged the last to major features for the Table API / SQL (time indicators and retraction support) to master. We will need to work on some smaller issues for those features which will take a few more days (1 week max), but the big changes are in. Working on those final issue does not block a release candidate. The Table API / SQL are on top of the DataStream API and runtime. So the last fixes won't interfere with testing the lower levels of the system. Cheers, Fabian 2017-05-05 21:02 GMT+02:00 Stephan Ewen: > Yes, I second Ufuk, thanks Robert and Aljoscha for the effort. > > Thanks to the community for hard work on the features. > > On Fri, May 5, 2017 at 4:03 PM, Ufuk Celebi wrote: > > > On Fri, May 5, 2017 at 3:59 PM, Stephan Ewen wrote: > > > Also, if no release candidate would be created today, it would not make > > any > > > difference anyways... > > > > If no one tests a RC (if created today) over the weekend it also > > wouldn't make a difference. ;-) > > > > Thanks to all for chiming in here and Robert and Aljoscha especially > > for making sure that everyone is on the same page wrt blockers etc. > > >