[
https://issues.apache.org/jira/browse/FLINK-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223811#comment-15223811
]
Aljoscha Krettek commented on FLINK-3669:
-----------------------------------------
Yes, you are right about that one. I think the way to go is to just not
serialize the {{SchedulesFuture}}. Upon restore we have to set a timer on
{{System.currentTimeMillis()}}, this will trigger any of the other timers that
should fire.
About storing the {{ScheduledFuture}}s. That's seems tricky. If we don't do the
coalescing we have an additional map that we always have to check. If we do
coalescing then we have to keep track of how many timers are coalesced into one
timer before we can cancel the future.
> WindowOperator registers a lot of timers at StreamTask
> ------------------------------------------------------
>
> Key: FLINK-3669
> URL: https://issues.apache.org/jira/browse/FLINK-3669
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.0.1
> Reporter: Aljoscha Krettek
> Priority: Blocker
>
> Right now, the WindowOperator registers a timer at the StreamTask for every
> processing-time timer that a Trigger registers. We should combine several
> registered trigger timers to only register one low-level timer (timer
> coalescing).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
