shangeyao opened a new issue, #4508: URL: https://github.com/apache/streampark/issues/4508
## Problem Flink SQL jobs fail to start reliably on **Yarn Application** and **Kubernetes Application** mode when using Flink 2.x (e.g. 2.0.2, 2.2.1). Symptoms include: - Yarn Application: missing dependencies (snakeyaml), incorrect user jar / classpath, Flink 2.x `ParameterTool` API relocation, and shims JAR ordering conflicts in the fat jar. - Kubernetes Application: SqlClient logback initialization fails under parent-first classloading; Flink SQL docker image build misses snakeyaml. - Kubernetes Session: cluster health check did not treat session clusters like remote clusters for REST reachability. ## Expected behavior Users should be able to create, release, start, and cancel Flink SQL applications on Yarn/K8s Application mode with Flink 2.x the same way as Flink 1.x. ## Proposed fix - Build and submit a per-application fat jar for Yarn Application SQL jobs; include snakeyaml and correct shim merge order. - Add `FlinkParameterToolBridge` so SqlClient works with Flink 1.x and 2.x `ParameterTool` packages. - Load logback configuration from classpath URL streams and rewrite shaded class names (fix K8s Application SqlClient startup). - Bundle snakeyaml into K8s Application docker images for Flink SQL. - Stop adding shims artifacts to Yarn Application `provided.lib.dirs`. - Treat Kubernetes Session clusters as HTTP-remotable in `FlinkClusterWatcher`. - Increase Kubernetes session cluster deploy/shutdown wait timeout for slow environments. -- 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]
