[jira] [Updated] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

2020-08-27 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated FLINK-18695:
---
Labels: pull-request-available  (was: )

> 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
>Assignee: Yun Gao
>Priority: Major
>  Labels: pull-request-available
> 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)


[jira] [Updated] (FLINK-18695) Allow NettyBufferPool to allocate heap buffers

2020-07-24 Thread Chesnay Schepler (Jira)


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

Chesnay Schepler updated FLINK-18695:
-
Description: 
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]

  was:
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]


> 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)