-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About RefreshScopeRefreshedEvent #4283
Comments
@OlgaMaciaszek Hi, is there any update? |
Hi @shawnplay, I hope we'll be able to discuss this at today's team meeting. Will post any updates here. |
Hi @shawnplay - what is your specific scenario here? Please provide more detail or some code snippet of how you would like to use the name in your usecase. |
I am using hot update of spring cloud config, but this event is triggered, causing my eureka instance to experience a brief restart |
We are still not sure, how you propose to handle this event based on name (against what to check the name of the event). Do you have any suggestions? |
I'm wondering, why do you need to listen to the RefreshScopeRefreshedEvent event and then re-register the Eureka instance? |
I found that the propagation of any
RefreshScopeRefreshedEvent
event will cause Eureka to restart. I think this is unreasonable. The event object already contains the name of the configuration object refreshed. You should check whether this name belongs to you before restarting.The text was updated successfully, but these errors were encountered: