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

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

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> 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.3.4#803005)

Reply via email to