beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (BEAM-175) Don't leak garbage collection timers in GlobalWindow
Date Thu, 23 Mar 2017 05:10:41 GMT

     [ https://issues.apache.org/jira/browse/BEAM-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kenneth Knowles reassigned BEAM-175:
------------------------------------

    Assignee:     (was: Kenneth Knowles)

> 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
>
> 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.15#6346)

Mime
View raw message