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 Fri, 29 Apr 2016 12:21:12 GMT

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

Aljoscha Krettek commented on FLINK-3669:

Ah, in the custom trigger the {{oldTimestamp}} field is problematic. One {{Trigger}} instance
is used for all the different keys, this means that the field will change in between {{onElement()}}
calls for the same key if {{onElement()}} is called in the meantime for a different key.

For the timestamp a {{ValueState}} could be used, the states are kept separately for each
key. For an example, {{CountTrigger}} is good, it's also the only {{Trigger}} we currently
have in Flink that uses trigger state.

> 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