You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/05/06 16:59:00 UTC

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

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

ASF GitHub Bot logged work on BEAM-9308:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/May/20 16:58
            Start Date: 06/May/20 16:58
    Worklog Time Spent: 10m 
      Work Description: stale[bot] commented on pull request #10852:
URL: https://github.com/apache/beam/pull/10852#issuecomment-624768356


   This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any 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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 431314)
    Time Spent: 2h  (was: 1h 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: 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)