[
https://issues.apache.org/jira/browse/BEAM-7112?focusedWorklogId=234523&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-234523
]
ASF GitHub Bot logged work on BEAM-7112:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Apr/19 13:36
Start Date: 29/Apr/19 13:36
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-487582405
> I think this is good to merge. Let's tackle problems with the checkpoint
interaction next. On Flink >= 1.6 this would be trivial to solve by flushing
in`preSnapshotBarrier`. For 1.5 we will have to do one of the following:
>
> 1. Checkpoint cleanup timers and defer execution for after the checkpoint
> 2. Buffer emitted elements during snapshot (this is already done but there
is no key scope)
The issues is that a new bundles is created during finish bundle, which is
actually not related to this PR. Tracked in:
https://issues.apache.org/jira/browse/BEAM-7171
----------------------------------------------------------------
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: 234523)
Time Spent: 9h 10m (was: 9h)
> 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: 9h 10m
> 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)
