Replies: 3 comments 3 replies
-
What has happened to your Redis instances meanwhile? Were there any DNS or IP address changes? These typically cause outcomes like that one you've described. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@mp911de is there any other configuration to set to detect any changes in the cluster in java code. Can you please let me know, |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi All, Can you please let me know how to address the issue, when the master IP changes in redis cluster. Is this an issue in lettuce-core? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Everyone,
We have an Spring application deployed in CloudFoundry and using LettuceConnectionFactory to connect to redis. Started getting error "io.lettuce.core.RedisCommandTimeoutException: Command timed out after 1 minute(s)" recently but however the application was deployed months back and there were no changes in application. After talking to our internal platform team, deleted the application and re-deployed, re-binded the redis service which made the connection to redis successful.
Request you share your feedback.
Environment details
Spring-boot version 2.6.6
Redis service is binded to the spring applications
Deployed in CloudFoundry
The connection factory is created on application boot up
The redis service contains below details
"credentials": {
"hostname":
"master_name":
"password":
"port":
"sentinel_port":
}
Java code snippet
var sentinelConfig = new RedisSentinelConfiguration().master(master_name).sentinel(hostname, sentinel_port); sentinelConfig.setPassword(RedisPassword.of(dbKey)); sentinelConfig.setSentinelPassword(RedisPassword.of(dbKey)); return new LettuceConnectionFactory(sentinelConfig);
Beta Was this translation helpful? Give feedback.
All reactions