[
https://issues.apache.org/jira/browse/FLINK-18695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168391#comment-17168391
]
Zhijiang commented on FLINK-18695:
----------------------------------
{quot}
How problematic would it be to backport this to older versions? (1.10, maybe
even 1.9?)
{quot}
I think it is up to the experiments results? If we convince the heap memory
overhead after upgrading is trivial, then it is simple to backport to older
versions. Otherwise we need estimate the other dependencies.
I already synced with [~gaoyunhaii] and he is willing to help handle it. Since
he is on vacation now, probably he can work on after next week. I assign this
ticket to him.
> Allow NettyBufferPool to allocate heap buffers
> ----------------------------------------------
>
> Key: FLINK-18695
> URL: https://issues.apache.org/jira/browse/FLINK-18695
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Reporter: Chesnay Schepler
> Priority: Major
> Fix For: 1.12.0
>
>
> in 4.1.43 netty made a change to their SslHandler to always use heap buffers
> for JDK SSLEngine implementations, to avoid an additional memory copy.
> However, our {{NettyBufferPool}} forbids heap buffer allocations.
> We will either have to allow heap buffer allocations, or create a custom
> SslHandler implementation that does not use heap buffers (although this seems
> ill-adviced?).
> /cc [~sewen] [~uce] [~NicoK] [~zjwang] [~pnowojski]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
