Jcodelove opened a new issue, #2732:
URL: https://github.com/apache/incubator-streampark/issues/2732

   ### 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
   
   1.8
   
   ### Scala Version
   
   2.12.x
   
   ### StreamPark Version
   
   latest
   DIGEST :cb5b91963239
   
   ### Flink Version
   
   1.15.3
   
   ### deploy mode
   
   kubernetes-session
   
   ### What happened
   
   The app run status is always STARTING when the app runing(JobManager can see 
the corresponding task also k8s can see the corresponding pod). The 
kubenetes-session and kubenetes-application both have this problem.
   
   
   
   
   
   ### Error Exception
   
   ```log
   15:44:00.141 [ForkJoinPool-1-worker-0] WARN 
org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - Failed 
to visit remote flink jobs on kubernetes-native-mode cluster, and the retry 
access logic is performed.
   ```
   
   
   ### Screenshots
   
   
![image](https://user-images.githubusercontent.com/76688605/236610609-d3406edc-dc27-4919-add5-97add6a96108.png)
   
![image](https://user-images.githubusercontent.com/76688605/236610726-f75a7e80-3ae8-44c0-9970-d7972b793078.png)
   
   
![image](https://user-images.githubusercontent.com/76688605/236610752-63d803a8-ae3c-40db-a026-e206e45c3d83.png)
   
![image](https://user-images.githubusercontent.com/76688605/236610769-5356d260-3b75-49cc-b1bf-412540576470.png)
   
   ### Are you willing to submit PR?
   
   - [ ] 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]

Reply via email to