[
https://issues.apache.org/jira/browse/BEAM-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145669#comment-17145669
]
Beam JIRA Bot commented on BEAM-175:
------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> Don't leak garbage collection timers in GlobalWindow
> ----------------------------------------------------
>
> Key: BEAM-175
> URL: https://issues.apache.org/jira/browse/BEAM-175
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Mark Shields
> Priority: P3
>
> Consider the transform:
> Window
> .into(new GlobalWindows())
> .triggering(
> Repeatedly.forever(
> AfterProcessingTime.pastFirstElementInPane().plusDelayOf(...)))
> .discardingFiredPanes()
> This is a common idiom for 'process elements bunched by arrival time'.
> Currently we create an end-of-window timer per key, which clearly will only
> fire if the pipeline is drained.
> Better would be to avoid creating end-of-window timers if there's no state
> which needs to be processed at end-of-window (ie at drain if the Global
> window).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
