flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3669) WindowOperator registers a lot of timers at StreamTask
Date Tue, 12 Apr 2016 10:33:25 GMT

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

Aljoscha Krettek commented on FLINK-3669:

I finally had a look at your code. It looks good but the timer coalescing is only local to
one key, i.e. if two different keys register a timer for time t we still register two timers
on the {{ScheduledThreadPoolExecutor}}. Have you had a chance to test it with your job where
you originally discovered the problem that the timers are not garbage collected? Maybe with
the timer cleanup it is already sufficient without doing coalescing across keys.

> 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
>            Assignee: Konstantin Knauf
>            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

View raw message