xinzhuxiansheng opened a new issue, #4220:
URL: https://github.com/apache/streampark/issues/4220

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/streampark/issues?q=is%3Aissue+label%3A%22improvement%22)
 and found no similar issues.
   
   
   ### Java Version
   
   jdk1.8
   
   ### Scala Version
   
   2.12.x
   
   ### StreamPark Version
   
   2.1.5
   
   ### Flink Version
   
   flink version 1.15.3
   
   ### Deploy mode
   
   kubernetes-application
   
   ### What happened
   
   I encountered a problem when upgrading the existing streampark environment 
2.1.3 to version 2.1.5. As shown below, the log will continuously print 
"[StreamPark] Get flinkClient error, the error is: 
io.fabric8.kubernetes.client.KubernetesClientException: An error has 
occurred.", and eventually the StreamPark service will trigger an OOM 
exception, causing the Pod to die. However, these exception logs cannot provide 
me with a basis for investigation. I think it must be optimized here, which can 
tell me which job caused it.
   
   我在处理已有的 streampark 环境2.1.3,升级到 2.1.5 版本时遇到的问题,如下所示, log 会不断打印 “[StreamPark] 
Get flinkClient error, the error is: 
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.  
”, 最终 StreamPark 服务会触发 OOM异常,而导致 Pod 死亡。   但是这些异常 log 
无法给我提供排查依据,我想这里肯定优化它,它可以告诉我是哪个job引起的。
   
   
   
   ### Error Exception
   
   ```log
   [StreamPark] Get flinkClient error, the error is: 
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
   ```
   
   ### Screenshots
   
   
   
![Image](https://github.com/user-attachments/assets/65aec56d-9150-413a-b0c3-cb41a53994cc)
   
   ### 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