[jira] [Comment Edited] (FLINK-3669) WindowOperator registers a lot of timers at StreamTask

["Aljoscha Krettek (JIRA)" <ji...@apache.org>]

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

Aljoscha Krettek edited comment on FLINK-3669 at 4/1/16 12:05 PM:
------------------------------------------------------------------

Yes, the 3rd option would require additional documentation and care on the part of users, so I would probably not go for it. I'll try and come up with a quick prototype for 1. to see how it behaves. Unless you want to work on it.

I also found another problem. The queue that is used for the triggers turns out to be a bottleneck because removing items from it is O\(n\), so with very large key ranges this becomes very slow.


was (Author: aljoscha):
Yes, the 3rd option would require additional documentation and care on the part of users, so I would probably not go for it. I'll try and come up with a quick prototype for 1. to see how it behaves. Unless you want to work on it.

I also found another problem. The queue that is used for the triggers turns out to be a bottleneck because removing items from it is O(n), so with very large key ranges this becomes very slow.

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