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
Observing that lettuce client fails to process commands successfully after 3-4 days of successful deployments and working.
The current client options are
We see the above error and after that all the requests are rejected. Is there some issue in the configuration settings? The process we follow for creating a connection with AWS ElastiCache is as follows,
Assume a role that provides with SessionToken
Pass that to a Class that extends RedisCredentialsProvider which resolvesCredentials (public Mono resolveCredentials())
Input Code
Input Code
// your code here;
Expected behavior/code
The reconnection should happen
Environment
Lettuce version(s): 6.5.1.RELEASE
Redis version: 7.1.0
Questions
What is the correct ClientOptions to use in production to allow re-connect. Is it advised to have all three together?
.autoReconnect(true))
.suspendReconnectOnProtocolFailure(true)
.disconnectedBehavior(ClientOptions.DisconnectedBehavior.REJECT_COMMANDS)
Based on the above settings, reconnect is suspended. how should we recover from this?
Restarting the deployment fixed the issue. However we cannot restart the deployment everytime. Please do provide if any documentation that explains the best practices to connect when using AWS ElastiCache
The text was updated successfully, but these errors were encountered:
Bug Report
Observing that lettuce client fails to process commands successfully after 3-4 days of successful deployments and working.
The current client options are
Current Behavior
Stack trace
We see the above error and after that all the requests are rejected. Is there some issue in the configuration settings? The process we follow for creating a connection with AWS ElastiCache is as follows,
Input Code
Input Code
// your code here;
Expected behavior/code
The reconnection should happen
Environment
Questions
What is the correct ClientOptions to use in production to allow re-connect. Is it advised to have all three together?
.autoReconnect(true))
.suspendReconnectOnProtocolFailure(true)
.disconnectedBehavior(ClientOptions.DisconnectedBehavior.REJECT_COMMANDS)
Based on the above settings, reconnect is suspended. how should we recover from this?
Restarting the deployment fixed the issue. However we cannot restart the deployment everytime. Please do provide if any documentation that explains the best practices to connect when using AWS ElastiCache
The text was updated successfully, but these errors were encountered: