laywin opened a new issue, #6223:
URL: https://github.com/apache/incubator-seata/issues/6223

   <!-- Please do not use this issue template to report security 
vulnerabilities but refer to our [security 
policy](https://github.com/seata/seata/security/policy). -->
   
   ## Why you need it?
    Is your feature request related to a problem? Please describe in details
   目前在spring boot环境下,seata感知不到环境变量的改变,即使配置中心已经将配置推送到了应用程序的environment, 
这里配置中心并不是为seata单独开启的配置中心,感觉这种情况很普遍. 
我看了一下因为存在configurationCache不会读取最新的配置,并且fileConfiguration的轮询获取最新配置被关闭了,看了一下之前存在这个pr:
 https://github.com/apache/incubator-seata/pull/3991 , 
曾今我也被pr里面的问题疑惑过...,不过我觉得可以换一种方式解决一下.
   
   Currently in the spring boot environment, seata cannot sense changes in 
environment variables. Even if the configuration center has pushed the 
configuration to the application environment, the configuration center here is 
not a separate configuration center for seata. I feel that this situation is 
very common. I I took a look because the configurationCache will not read the 
latest configuration, and the polling of fileConfiguration to obtain the latest 
configuration is turned off. See: 
https://github.com/apache/incubator-seata/pull/3991. I have also I was confused 
by https://github.com/apache/incubator-seata/pull/3991, but I think it can be 
solved in another way.
   
   ## How it could be?
   A clear and concise description of what you want to happen. You can explain 
more about input of the feature, and output of it.
   
   
   ## Other related information
   Add any other context or screenshots about the feature request here.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to