You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:13 UTC

[jira] [Commented] (BEAM-9308) Optimize state cleanup at end-of-window

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

Beam JIRA Bot commented on BEAM-9308:
-------------------------------------

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.


> Optimize state cleanup at end-of-window
> ---------------------------------------
>
>                 Key: BEAM-9308
>                 URL: https://issues.apache.org/jira/browse/BEAM-9308
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Steve Niemitz
>            Priority: P2
>              Labels: stale-P2
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> When using state with a large keyspace, you can end up with a large amount of state cleanup timers set to fire all 1ms after the end of a window.  This can cause a momentary (I've observed 1-3 minute) lag in processing while windmill and the java harness fire and process these cleanup timers.
> By spreading the firing over a short period after the end of the window, we can decorrelate the firing of the timers and smooth the load out, resulting in much less impact from state cleanup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)