You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2019/10/24 08:58:00 UTC

[jira] [Closed] (FLINK-14156) Execute/run processing timer triggers taking into account operator level mailbox loops

     [ https://issues.apache.org/jira/browse/FLINK-14156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski closed FLINK-14156.
----------------------------------
    Fix Version/s: 1.10.0
       Resolution: Fixed

Merged as c83f7244e1fdb940efb0df8716f49ae681199312..432efb3e7b12aa71a56464c7651181c28b1c652d

> Execute/run processing timer triggers taking into account operator level mailbox loops
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-14156
>                 URL: https://issues.apache.org/jira/browse/FLINK-14156
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Task
>            Reporter: Alex
>            Assignee: Alex
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> With FLINK-12481, the timer triggers are executed by the mailbox thread and passed to the mailbox with the maximum priority.
> In case of operators that use {{mailbox.yield()}} (introduced in FLINK-13248), current approach may execute timer triggers that belong to an upstream operator. Such timer trigger, may potentially call {{processElement|Watermark()}} which eventually would come back to the current operator. This situation may be similar to FLINK-13063.
> To avoid this, the proposal is to set mailbox letters priorities of timer triggers with the priority of the operator that the trigger belongs to.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)