[
https://issues.apache.org/jira/browse/BEAM-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132175#comment-17132175
]
Beam JIRA Bot commented on BEAM-175:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
