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/01/10 09:32:00 UTC

[jira] [Closed] (FLINK-7517) let NettyBufferPool extend PooledByteBufAllocator

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

Nico Kruber closed FLINK-7517.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Merged.

1.5.0: fcdd56e548ddd1bd7475970bdc5718b7b18d9803

> let NettyBufferPool extend PooledByteBufAllocator
> -------------------------------------------------
>
>                 Key: FLINK-7517
>                 URL: https://issues.apache.org/jira/browse/FLINK-7517
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>    Affects Versions: 1.4.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>             Fix For: 1.5.0
>
>
> {{NettyBufferPool}} wraps {{PooledByteBufAllocator}} but due to this, any allocated buffer's {{alloc()}} method is returning the wrapped {{PooledByteBufAllocator}} which allowed heap buffers again. By extending the {{PooledByteBufAllocator}}, we prevent this loop hole and also fix the invariant that a copy of a buffer should have the same allocator.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)