[jira] [Commented] (FLINK-4651) Re-register processing time timers at the WindowOperator upon recovery.

["Scott Kidder (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812288#comment-15812288 ] 

Scott Kidder commented on FLINK-4651:
-------------------------------------

I can confirm that this issue appears to be fixed in the release-1.2.0-rc0 branch (commit f3c59cedae7a508825d8032a8aa9f5af6d177555).

> Re-register processing time timers at the WindowOperator upon recovery.
> -----------------------------------------------------------------------
>
>                 Key: FLINK-4651
>                 URL: https://issues.apache.org/jira/browse/FLINK-4651
>             Project: Flink
>          Issue Type: Bug
>          Components: Windowing Operators
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>              Labels: windows
>             Fix For: 1.2.0, 1.1.5
>
>
> Currently the {{WindowOperator}} checkpoints the processing time timers, but upon recovery it does not re-registers them with the {{TimeServiceProvider}}. To actually reprocess them it relies on another element that will come and register a new timer for a future point in time. Although this is a realistic assumption in long running jobs, we can remove this assumption by re-registering the restored timers with the {{TimeServiceProvider}} in the {{open()}} method of the {{WindowOperator}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)