You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2016/09/21 08:33:20 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kostas Kloudas updated FLINK-4651:
----------------------------------
    Description: 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}}}.  (was: 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}}}.)

> 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.1.3
>
>
> 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)