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

   ## What is the purpose of the change
   
   The heavy deployment end-to-end test fails on the Azure Java 11 nightlies 
(10 of 198 runs since 2026-08-01) with OutOfMemoryError: Metaspace. Its 
TaskManagers reach about 64 MiB of committed metaspace, which is the limit the 
test sets.
   
   ## Brief change log
   
     - Raise `taskmanager.memory.jvm-metaspace.size` from 64m to 96m
     - Raise `taskmanager.memory.process.size` from 1024m to 1056m, so the heap 
stays at 440 MiB
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as the heavy 
deployment end-to-end test itself. Locally on Java 11 (x86_64 under emulation, 
2 CPUs) the TaskManagers peak at 61-64 MiB committed metaspace both with 64m 
and with 96m, and the heap stays at 440 MiB. The failure does not reproduce 
locally, so the nightlies will tell.
   
   ## 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: 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
   
   ---
   
   ##### 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