You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2023/05/06 02:42:00 UTC

[jira] [Closed] (FLINK-31764) Get rid of numberOfRequestedOverdraftMemorySegments in LocalBufferPool

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

Weijie Guo closed FLINK-31764.
------------------------------
    Fix Version/s: 1.18.0
                   1.17.1
       Resolution: Fixed

master(1.18) via 3379c2c085da43bb452536c981a7fc13f39482ee.
release-1.17 via 2edc003004d0d0f1e40ef2b7e14189965183f46c.

> Get rid of numberOfRequestedOverdraftMemorySegments in LocalBufferPool
> ----------------------------------------------------------------------
>
>                 Key: FLINK-31764
>                 URL: https://issues.apache.org/jira/browse/FLINK-31764
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Network
>    Affects Versions: 1.18.0
>            Reporter: Weijie Guo
>            Assignee: Weijie Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.18.0, 1.17.1
>
>
> After FLINK-31763, we don't need the specific field {{numberOfRequestedOverdraftMemorySegments}} to record the overdraft buffers has been requested anymore since we regard all buffers exceeding the \{{currentPoolSize}} as overdraft.



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