Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS RedisCache replica Failover can not be resolved #2872

Open
musicallyvk opened this issue Jun 5, 2024 · 1 comment
Open

AWS RedisCache replica Failover can not be resolved #2872

musicallyvk opened this issue Jun 5, 2024 · 1 comment
Labels
for: stackoverflow A question that is better suited to stackoverflow.com status: waiting-for-feedback We need additional information before we can continue

Comments

@musicallyvk
Copy link

musicallyvk commented Jun 5, 2024

Hi Everyone, Hope everyone is doing great!

I know this issue might not related to lettiuce but because it is redis then might be someone would have encountered the same.

so i have a 3 replica and 1 primary on aws elasticache redisCache using version 4.0, with the redis config file on the application level which has a load balancer with round robbin and using replicatedServersConfig. and many other things like retry , failedSlaveCheckInterval,timeout, readMode , subscriptionMode and many things.

now the thing is if a failover happens then some requests are still being routed to that failed node, how to get it resolved, anyone please help me. i am stuck with this for months.
Thanks Already !

if you need more details on config then -

{
   "replicatedServersConfig":{
      "idleConnectionTimeout":10000,
      "connectTimeout":10000,
      "timeout":30000,
      "retryAttempts":3,
      "retryInterval":1500,
      "failedSlaveReconnectionInterval":3000,
      "failedSlaveCheckInterval":60000,
      "password":"*****",
      "subscriptionsPerConnection":5,
      "clientName":"myClientName",
      "loadBalancer":{
         "class":"org.redisson.connection.balancer.RoundRobinLoadBalancer"
      },
      "subscriptionConnectionMinimumIdleSize":1,
      "subscriptionConnectionPoolSize":50,
      "slaveConnectionMinimumIdleSize":24,
      "slaveConnectionPoolSize":64,
      "masterConnectionMinimumIdleSize":24,
      "masterConnectionPoolSize":64,
      "readMode":"SLAVE",
      "subscriptionMode":"SLAVE",
      "nodeAddresses":[
         "rediss://Node1,Node2,Node3,Node4"
      ],
      "scanInterval":1000
   },
   "threads":16,
   "nettyThreads":32,
   "codec":{
      "class":"org.redisson.codec.LZ4Codec"
   },
   "transportMode":"NIO"
}
@tishun tishun added the for: stackoverflow A question that is better suited to stackoverflow.com label Jun 6, 2024
@tishun
Copy link
Collaborator

tishun commented Jun 28, 2024

Hey @musicallyvk ,

I assume - since you are using a load balancer - that the Lettuce driver is set up in a way that it only connects to the load balancer? If so this seems very specific to the AWS configuration I doubt you will find much help here. Have you tried asking in a public forum like stackoverflow? Or one that covers AWS?

@tishun tishun added the status: waiting-for-feedback We need additional information before we can continue label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: stackoverflow A question that is better suited to stackoverflow.com status: waiting-for-feedback We need additional information before we can continue
Projects
None yet
Development

No branches or pull requests

2 participants