beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Shields (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-175) Leak garbage collection timers in GlobalWindow
Date Tue, 05 Apr 2016 23:22:26 GMT

    [ https://issues.apache.org/jira/browse/BEAM-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227344#comment-15227344
] 

Mark Shields commented on BEAM-175:
-----------------------------------

For the Global window every pane will be EARLY, so it is just getIndex standing between us
and nirvana.

I'll code up a fix which replaces the monotonic index with a random, fix the timers, and we
can at least see where we're at.

> 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
>            Assignee: Mark Shields
>
> 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
(v6.3.4#6332)

Mime
View raw message