|
Answer» There can be 2 possible causes: - Client-side causes:
- The application might have been redeployed.
- The application might have just performed a SCALING operation.
- The client-side networking layer has been changed.
- There might be TRANSIENT errors in the client or the NETWORK between the client and the server.
- Another possible reason could be the bandwidth threshold limits have been crossed.
- Server-side causes:
- It might occur if the Azure Redis Cache SERVICE itself might undergo a failover from the primary to the secondary node.
- The server instance where the cache was deployed might have undergone patching or maintenance.
|