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
For a variety of reasons, it's possible that a cmsd has a transient issue which prevents it from responding to location request.
Correspondingly, we should have the ability to do a separate timeout for a negative response and a positive response. For example, we might want to have a 15 minute timeout for cache entries with no location but 8 hours for a cache entry with at least one server location.
It's OK if "negative response" here is defined to mean "all servers respond negatively"; no need to try to tackle the case of a subset of servers.
The text was updated successfully, but these errors were encountered:
For a variety of reasons, it's possible that a
cmsd
has a transient issue which prevents it from responding to location request.Correspondingly, we should have the ability to do a separate timeout for a negative response and a positive response. For example, we might want to have a 15 minute timeout for cache entries with no location but 8 hours for a cache entry with at least one server location.
It's OK if "negative response" here is defined to mean "all servers respond negatively"; no need to try to tackle the case of a subset of servers.
The text was updated successfully, but these errors were encountered: