You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2018/10/01 10:19:00 UTC

[jira] [Resolved] (FLINK-10339) SpillReadBufferPool cannot use off-heap memory

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

Nico Kruber resolved FLINK-10339.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

Fixed via:
- master: 2ab55df946dc35280f66c6f073a112b497acede3

> SpillReadBufferPool cannot use off-heap memory
> ----------------------------------------------
>
>                 Key: FLINK-10339
>                 URL: https://issues.apache.org/jira/browse/FLINK-10339
>             Project: Flink
>          Issue Type: Improvement
>          Components: Network
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
>            Reporter: zhijiang
>            Assignee: zhijiang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> Currently, the {{NetworkBufferPool}} always uses off-heap memory to reduce memory copy from flink {{Buffer}} to netty internal {{ByteBuf}} during transporting on sender side.
>  
> But for {{SpillReadBufferPool}} in {{SpilledSubpartitionView}}, it still uses heap memory for caching. We can make it as off-heap by default similar with {{NetworkBufferPool}} or decide the type by the current parameter {{taskmanager.memory.off-heap.}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)