[GitHub] NicoK opened a new pull request #7445: [FLINK-11154][network] bump Netty to 4.1.32

[GitBox <gi...@apache.org>]

NicoK opened a new pull request #7445: [FLINK-11154][network] bump Netty to 4.1.32
URL: https://github.com/apache/flink/pull/7445
 
 
   ## What is the purpose of the change
   
   This pull request bumps Netty to a newer version (4.1.32) for the following improvements/changes done since 4.1.24:
   - big improvements (performance, feature set) 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
   
   Please note that this PR is based on https://github.com/apache/flink-shaded/pull/55 and temporarily fetches from that repository to run the tests with the upgraded netty version.
   Beware NOT to merge the according commit marked as `[DO-NOT-MERGE]` - and then only merge it once a new version of `flink-shaded` has been released that contains the new Netty version.
   
   ## Brief change log
   
   - bump netty dependency
   - update `AbstractByteBufTest` to the updated code
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **yes**
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: **no**
     - The S3 file system connector: **no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
     - If yes, how is the feature documented? **not applicable**
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services