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.
Comment From: shawnplay
@OlgaMaciaszek Hi, is there any update?
Comment From: OlgaMaciaszek
Hi @shawnplay, I hope we'll be able to discuss this at today's team meeting. Will post any updates here.
Comment From: OlgaMaciaszek
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.
Comment From: shawnplay
I am using hot update of spring cloud config, but this event is triggered, causing my eureka instance to experience a brief restart
Comment From: OlgaMaciaszek
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?
Comment From: shawnplay
I'm wondering, why do you need to listen to the RefreshScopeRefreshedEvent event and then re-register the Eureka instance?