[
https://issues.apache.org/jira/browse/BEAM-9308?focusedWorklogId=391039&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-391039
]
ASF GitHub Bot logged work on BEAM-9308:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/20 03:32
Start Date: 22/Feb/20 03:32
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #10852: [BEAM-9308]
Decorrelate state cleanup timers
URL: https://github.com/apache/beam/pull/10852#issuecomment-589913248
Why is this problem specific to the GC timer? How about the normal
end-of-window timer that is used to fire windowed aggregations. For fixed
windows there is one per key and those also fire all at the same time.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 391039)
Time Spent: 1h (was: 50m)
> 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
> Assignee: Steve Niemitz
> Priority: Major
> Time Spent: 1h
> 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)
