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

Missing cache invalidation for remote region requests #118

Closed
NiteshKant opened this issue Apr 30, 2014 · 2 comments
Closed

Missing cache invalidation for remote region requests #118

NiteshKant opened this issue Apr 30, 2014 · 2 comments
Milestone

Comments

@NiteshKant
Copy link
Contributor

In situations where a discovery client is configured to fetch registry information also from remote region(s), the cache within the REST endpoint is not invalidated for any change in the local registry information. Instead it expires after the configured cache expiry time (defaults to 3 mins)

The reason for this behavior is that on invalidate() callback the keys it invalidates does not include the region names. Since, for the API calls that include the region parameter, the cache key is created with the region string, the invalidate call does not match that key. Hence, the cache does not get invalidated which results in no changes to the registry being visible to the client.

@NiteshKant NiteshKant added this to the 1.1.131 milestone May 2, 2014
NiteshKant pushed a commit to NiteshKant/eureka that referenced this issue May 7, 2014
ResponseCache entries when queried with a remote region, were not invalidated whenever any
local registry information changes.
NiteshKant added a commit that referenced this issue May 7, 2014
@NiteshKant
Copy link
Contributor Author

Available in 1.1.131

@bmpattanaik
Copy link

This issue is close . But how to change this default behavior (defaults to 3 mins).
I am facing issue with invalidating when it runs locally with one eureka server.
spring-cloud/spring-cloud-netflix#3652

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

2 participants