You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Steve Niemitz (Jira)" <ji...@apache.org> on 2022/01/12 14:43:00 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=17474592#comment-17474592 ] 

Steve Niemitz commented on BEAM-9308:
-------------------------------------

The attached PR is closed, we could never reach consensus on it and it was closed due to inactivity.  This issue is still valid and we still run something similar to the PR in our own fork.

> 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: P3
>          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.20.1#820001)