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

Posted to issues@flink.apache.org by "Jiangjie Qin (Jira)" <ji...@apache.org> on 2024/10/23 01:03:00 UTC

[jira] [Assigned] (FLINK-36585) The SplitFetcherManager.close() can chain the futures in a tight loop.

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

Jiangjie Qin reassigned FLINK-36585:
------------------------------------

    Assignee: Jiangjie Qin

> The SplitFetcherManager.close() can chain the futures in a tight loop.
> ----------------------------------------------------------------------
>
>                 Key: FLINK-36585
>                 URL: https://issues.apache.org/jira/browse/FLINK-36585
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Common
>    Affects Versions: 2.0-preview
>            Reporter: Jiangjie Qin
>            Assignee: Jiangjie Qin
>            Priority: Major
>             Fix For: 2.0.0
>
>
> This is an issue introduced in FLINK-35924. The SplitFetcherManager.close() may chain the fetcher status check to the element queue availability future in a tight loop. This may cause problems such as OOM if the fetcher closure takes long.
> The fix is straightforward. We just need to blocking waiting on each check.



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