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

   ## What is the purpose of the change
   
   SqlClientITCase fails consistently across all 3 CI pipelines (ci-e2e, 
cron_azure-e2e, cron_hadoop313-e2e) because the confluentinc/cp-kafka:7.2.2 
container crashes on startup with a NullPointerException in 
CgroupV2Subsystem.getInstance().
   
   This is a known JDK bug (JDK-8287073) present in JDK 11.0.16.1 (shipped in 
cp-kafka:7.2.2) and fixed in JDK 11.0.17+. Docker 29.1.x, rolled out on Azure 
runners on Feb 9, changed cgroup handling in a way that now triggers this bug. 
The JVM crashes during JMX agent initialization before Kafka can start.
   
   This pull request bumps both cp-kafka and cp-schema-registry from 7.2.2 to 
7.2.9 (the latest 7.2.x patch), which ships JDK 11.0.21 and includes the cgroup 
v2 fix.
   
   ## Brief change log
   
   - Updated from confluentinc/cp-kafka:7.2.2 to confluentinc/cp-kafka:7.2.9
   - Updated confluentinc/cp-schema-registry:7.2.2 to 
confluentinc/cp-schema-registry:7.2.9
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as SqlClientITCase 
and the schema registry E2E tests. These tests were previously failing due to 
the container crash and should now pass with the updated images.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (**yes** / no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't 
know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   


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