You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2024/08/02 11:03:00 UTC

[jira] [Closed] (FLINK-35933) Skip distributing maxAllowedWatermark if there are no subtasks

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

Roman Khachatryan closed FLINK-35933.
-------------------------------------
    Resolution: Fixed

cdf43aecafa33a50a4b4b6841c4cf505b195994a

> Skip distributing maxAllowedWatermark if there are no subtasks
> --------------------------------------------------------------
>
>                 Key: FLINK-35933
>                 URL: https://issues.apache.org/jira/browse/FLINK-35933
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Roman Khachatryan
>            Assignee: Roman Khachatryan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.20.0
>
>
> On JM, `SourceCoordinator.announceCombinedWatermark` executes unnecessary if there are no subtasks to distribute maxAllowedWatermark. This involves Heap and ConcurrentHashMap accesses and lots of logging.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)