[
https://issues.apache.org/jira/browse/BEAM-7112?focusedWorklogId=230088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-230088
]
ASF GitHub Bot logged work on BEAM-7112:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Apr/19 12:13
Start Date: 19/Apr/19 12:13
Worklog Time Spent: 10m
Work Description: mxm commented on pull request #8351: [BEAM-7112]
[flink] Defer state cleanup till bundle completion
URL: https://github.com/apache/beam/pull/8351#discussion_r276971673
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/translation/wrappers/streaming/ExecutableStageDoFnOperator.java
##########
@@ -402,6 +405,14 @@ private void setTimer(WindowedValue<InputT> timerElement,
TimerInternals.TimerDa
@Override
public void fireTimer(InternalTimer<?, TimerInternals.TimerData> timer) {
+ if (CleanupTimer.GC_TIMER_ID.equals(timer.getNamespace().getTimerId())) {
Review comment:
It would be great if we could just accumulate the state ids that need to be
cleaned up after the bundle finishes, instead of an indirection for timer
execution.
----------------------------------------------------------------
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: 230088)
Time Spent: 1h (was: 50m)
> 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
> Time Spent: 1h
> 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)
