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 this particular case, the customer might have so many client instances which were idle for quite a while. The clients held the stale address cache. Later when the clients tried to send the requests to the backend, it is possible that each client suffered the high latency once before the offline replica throws ConnectTimeoutException
Question for SDK team, can we have an infrequent timer to refresh the address cache for the case when there are already 4 replicas?
The text was updated successfully, but these errors were encountered:
For this particular case, the customer might have so many client instances which were idle for quite a while. The clients held the stale address cache. Later when the clients tried to send the requests to the backend, it is possible that each client suffered the high latency once before the offline replica throws ConnectTimeoutException
Question for SDK team, can we have an infrequent timer to refresh the address cache for the case when there are already 4 replicas?
The text was updated successfully, but these errors were encountered: