[
https://issues.apache.org/jira/browse/BEAM-7112?focusedWorklogId=233575&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-233575
]
ASF GitHub Bot logged work on BEAM-7112:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Apr/19 14:48
Start Date: 26/Apr/19 14:48
Worklog Time Spent: 10m
Work Description: tweise commented on issue #8399: [BEAM-7112] Timer race
with state cleanup - take two
URL: https://github.com/apache/beam/pull/8399#issuecomment-487084689
We don't need to checkpoint the cleanup queue since it does not cross the
bundle boundary. But we need to look into another issue (outside of this PR):
The finish bundle callback starts a new bundle when the watermark advances,
which can lead to inconsistent state snapshot.
----------------------------------------------------------------
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: 233575)
Time Spent: 7h 20m (was: 7h 10m)
> State cleanup interferes with user timer callback
> -------------------------------------------------
>
> Key: BEAM-7112
> URL: https://issues.apache.org/jira/browse/BEAM-7112
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.12.0
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: portability-flink
> Fix For: 2.13.0
>
> Time Spent: 7h 20m
> Remaining Estimate: 0h
>
> Cleanup timers and user timers are fired at the watermark. Processing of
> timers in the SDK worker is asynchronous, so it is possible that the state is
> already removed when the user timer callback executes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
