You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: