flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Knauf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3669) WindowOperator registers a lot of timers at StreamTask
Date Sun, 03 Apr 2016 16:55:25 GMT

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

Konstantin Knauf commented on FLINK-3669:
-----------------------------------------

I tried to implement the 1.. The hard part, I think, is to store the {{ScheduledFuture}}s
to in the {{WindowOperator}}. We could use a {{Map<Long,ScheduledFuture>}}, but this
only works if we also implement timer coalescing. Besides that I am unsure about how to de/serialize
this map. Could you give me pointer?

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

Mime
View raw message