[
https://issues.apache.org/jira/browse/FLINK-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16132125#comment-16132125
]
Nico Kruber commented on FLINK-7473:
------------------------------------
Another fix: properly fix your event time use (which is the reason for max int
in your case):
[Flink 1.3 Docs: Event
Time|https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/event_time.html]
states: "... the program needs to either use sources that directly define
event time for the data and emit watermarks themselves, or the program must
inject a Timestamp Assigner & Watermark Generator after the sources."
Various sub-topics go into more details, e.g. [Flink 1.3 Docs: Generating
Timestamps /
Watermarks|https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/event_timestamps_watermarks.html].
> Possible Leak in GlobalWindows
> ------------------------------
>
> Key: FLINK-7473
> URL: https://issues.apache.org/jira/browse/FLINK-7473
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
> Affects Versions: 1.3.2
> Environment: See attached project
> Reporter: Steve Jerman
> Attachments: timerIssue.zip
>
>
> Hi,
> I have been wrestling with a issue with GlobalWindows. It seems like it leaks
> instances of InternalTimer.
> I can't tell if it's a bug or my code so I created a 'minimal' project that
> has the issue...
> If you run the Unit Test in the attached and then monitor heap you will see
> that the number of InternalTimers continually increases. I added code to
> explicitly delete them.. doesn't seem to help.
> If I comment out registerEventTimeTimer ... no leak :)
> My suspicion is that PURGE/FIRE_AND_PURGE is leaving the timer in limbo.
> Steve
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
