[
https://issues.apache.org/jira/browse/BEAM-7785?focusedWorklogId=282544&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-282544
]
ASF GitHub Bot logged work on BEAM-7785:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/19 08:38
Start Date: 25/Jul/19 08:38
Worklog Time Spent: 10m
Work Description: iemejia commented on issue #9108: [BEAM-7785]
synchronize watermark update with bundle processing
URL: https://github.com/apache/beam/pull/9108#issuecomment-514953500
I am curious about the suggested data structure too. (even if we don't/can't
use it here)
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 282544)
Time Spent: 2h 20m (was: 2h 10m)
> DirectRunner: watermarks are updated asynchronously from bundle processing
> --------------------------------------------------------------------------
>
> Key: BEAM-7785
> URL: https://issues.apache.org/jira/browse/BEAM-7785
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Affects Versions: 2.13.0
> Reporter: Jan Lukavský
> Assignee: Jan Lukavský
> Priority: Major
> Fix For: 2.15.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Watermarks are updated in QuiescenceDriver (by calling fireTimers, which
> calls forceRefresh()) on WatermarkManager. This results in creating timer
> bundles, that are then processed asynchronously as DirectTransformExecutor.
> Because of that, watermarks (input watermarks mostly) might be updated while
> bundle is being processed. That violates assumption, that bundle processing
> should be atomical (with identical external conditions during processing of
> whole bundle).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
