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

   ### 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
   
   Java 8
   
   ### Scala Version
   
   2.12.x
   
   ### StreamPark Version
   
   dev
   
   ### Flink Version
   
   flink all version
   
   ### deploy mode
   
   kubernetes-session
   
   ### What happened
   
   The class loads InternalConfigHolder as a cache class, and an object is 
regenerated when used (it should be the same one, otherwise the cache will 
become invalid, and everything will become the default value)
   
   As follows:
   
   1. Springboot startup
   
![image](https://github.com/apache/incubator-streampark/assets/29968120/41f76abd-4fc4-4907-af8b-7c6bc9e0557a)
   
   2. Springboot startup is completed, and the yaml configuration is refreshed 
into InternalConfigHolder through EnvInitializer
   
![image](https://github.com/apache/incubator-streampark/assets/29968120/4b60b8d8-d92c-4075-a7ca-75f1e6f0d3c7)
   
   3. After springboot is started, click to start k8s sesssion deploy
   
![image](https://github.com/apache/incubator-streampark/assets/29968120/78a249b5-12b9-43e1-959c-8cf9e4823c7a)
   
   It can be seen that after passing this classloader, InternalConfigHolder 
regenerates an object
   
   
![image](https://github.com/apache/incubator-streampark/assets/29968120/583190d1-8447-4716-90ab-ba4c9d05e51b)
   
   
   ### Error Exception
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### 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