You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/02/16 08:46:00 UTC
[jira] [Closed] (FLINK-11154) Upgrade Netty to 4.1.32
[ https://issues.apache.org/jira/browse/FLINK-11154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-11154.
------------------------------------
Resolution: Fixed
master: 876f9919de987c78724f707f57b220654ca600a4
> Upgrade Netty to 4.1.32
> -----------------------
>
> Key: FLINK-11154
> URL: https://issues.apache.org/jira/browse/FLINK-11154
> Project: Flink
> Issue Type: Improvement
> Components: Network
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0, shaded-6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Notable changes since 4.1.24 (currently used in Flink 1.6-1.7):
> - big (performance, feature set) improvements for using openSSL based SSL engine (useful for FLINK-9816)
> - allow multiple shaded versions of the same netty artifact (as long as the shaded prefix is different)
> - Ensure ByteToMessageDecoder.Cumulator implementations always release.
> - Don't re-arm timerfd each epoll_wait
> - Use a non-volatile read for ensureAccessible() whenever possible to reduce overhead and allow better inlining.
> - Do not fail on runtime when an older version of Log4J2 is on the classpath
> - Fix leak and corruption bugs in CompositeByteBuf
> - Add support for TLSv1.3
> - Harden ref-counting concurrency semantics
> - bug fixes
> - Java 9-12 related fixes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)