FrommyMind opened a new issue, #4112: URL: https://github.com/apache/incubator-streampark/issues/4112
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-streampark/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### Java Version JDK1.8 ### Scala Version 2.12.x ### StreamPark Version 1. release-2.1.4 2. release-2.1.5-rc1 ### Flink Version 1.17.2 ### deploy mode kubernetes-session ### What happened After building Streampark, I started the console-server using the IDE, and then tried to start an Flink SQL Demo sample job in a Kubernetes session using Flink, but the status of the job was not updated correctly and remained "STARING". But on the Flink cluster Web UI, the job is already started and finally completed.   And the console log show that "tracking flink job status on kubernetes native session mode timeout" ``` 10:26:49.972 [pool-10-thread-1] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] [FlinkJobStatusWatcher] tracking flink job status on kubernetes native session mode timeout, limitSeconds=120, trackIds=TrackId(kubernetes-session,pre-flink,dev-k8s,100000,19308092faf9eb315b31fcf01fe0fdd3,100000,{jobmanager.execution.failover-strategy=region, fs.s3a.secret.key=test-user, state.checkpoints.dir=s3://flink-checkpoint/checkpoints/, rest.bind-address=localhost, taskmanager.numberOfTaskSlots=1, jobmanager.rpc.address=localhost, state.savepoints.dir=s3://flink-checkpoint/savepoints/, taskmanager.bind-host=localhost, jobmanager.bind-host=localhost, jobmanager.memory.process.size=1600m, state.backend.incremental=true, parallelism.default=1, fs.s3a.endpoint=10.191.80.169:9001, containerized.master.env.ENABLE_BUILT_IN_PLUGINS=flink-s3-fs-hadoop-1.17.2.jar, containerized.taskmanager.env.ENABLE_BUILT_IN_PLUGINS=flink-s3-fs-hadoop-1.17.2.jar, rest.address=loc alhost, fs.s3a.list.version=1, jobmanager.rpc.port=6123, fs.s3a.connection.ssl.enabled=false, fs.s3a.access.key=test-user, taskmanager.host=localhost, taskmanager.memory.process.size=1728m, s3.path.style.access=true}) ``` Then I tried to figure out what was going on. After some debugging, I modified the code as follows. ``` private def callJobsOverviewsApi(restUrl: String): Option[JobDetails] = { try { JobDetails.as( Request .get(s"$restUrl/jobs/overview") .connectTimeout(KubernetesRetriever.FLINK_REST_AWAIT_TIMEOUT_SEC) .responseTimeout(KubernetesRetriever.FLINK_CLIENT_TIMEOUT_SEC) .execute .returnContent() .asString(StandardCharsets.UTF_8) ) }catch { case e: Throwable => logWarn(e.toString) None } } ``` The I found some exeception output. ``` 10:37:42.660 [pool-10-thread-3] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats 10:37:42.661 [pool-10-thread-3] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats 10:37:47.660 [pool-10-thread-7] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats ``` ### Error Exception ```log 10:37:42.660 [pool-10-thread-3] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats 10:37:42.661 [pool-10-thread-3] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats 10:37:47.660 [pool-10-thread-7] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] java.lang.NoClassDefFoundError: org/json4s/Formats ``` ### Screenshots _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR!(您是否要贡献这个PR?) ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
