Skip to content
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

DiscoveryClient failed to fire events to EurekaNotificationServerListUpdater after cache refreshed #506

Open
WilliamChen-luckbob opened this issue Oct 20, 2022 · 0 comments

Comments

@WilliamChen-luckbob
Copy link

I have my application running in a hot refresh mode which means to make my application refresh it's configuration as soon as I change the config files, and this movement will trigger a RefreshEvent by ApplicationContext.

While using EurekaNotificationServerListUpdater as ServerListUpdater DiscoveryClient will lose all eurekaListeners registered by EurekaNotificationServerListUpdater after spring receiving a RefreshEvent.

After firing RefreshEvent, EurekaNotificationServerListUpdater for each service in each ribbon client will not change, which means, new DiscoveryClient will no longer trigger a CacheRefreshedEvent because none of the EurekaEventListener are in the new DiscoveryClient's listener list.

Is it possible to make a re-registration after RefreshEvent ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant