MartijnVisser opened a new pull request, #29831:
URL: https://github.com/apache/flink/pull/29831

   ## What is the purpose of the change
   
   Since FLINK-38912, flink-rpc-akka bundles a relocated Netty that duplicates 
flink-shaded-netty. The RPC class loader loads `org.apache.flink` classes 
component-first, so every JobManager and TaskManager loads about 4 MiB of Netty 
classes twice. That pushes the heavy deployment test over its 64m metaspace 
limit on Java 11 (FLINK-40788).
   
   ## Brief change log
   
     - Make `netty-handler` and `netty-transport` test-scoped in flink-rpc-akka 
again, as `netty-all` was before FLINK-38912
     - Remove the Netty entries and notices from the module's NOTICE, the Netty 
license files and the Netty shade filter
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as 
`PekkoRpcSystemLoaderITCase` and `RpcSSLAuthITCase`, which pass on Java 11 and 
17. On Java 11 the heavy deployment test's TaskManagers now peak at 54 MiB of 
metaspace instead of 57 MiB, and the test passes at 64m again.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - 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, Kubernetes/Yarn, ZooKeeper: yes
     - 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
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Claude Opus 5.5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to