Closed vasundhara785 closed 3 years ago
This may due to wrong redis cluster network configuration. You can add a breakpoint at here to see if the node info of slots is match with your given Addrs in clusterOptions.
This does not look like a go-redis problem. Besides v6 is quiet old.
Hey @vasundhara785 we ran into the same problem recently, CPU was ok but getting the same error dial tcp x.x.x.x:6380: i/o timeout
were you able to solve this issue?
Can we replicate the same to test/verify if there is some issue with the library?
FYI we are also using a similar version of the library.
Iam facing the same problem with the error dial tcp x.x.x.x:6380: i/o timeout . Does the operations (GET,SET ) made on redis would also create a client connection internally?
More insights: redis version : v6.15.8 one connection is opened and redis operations are made on the same connection. Its showing more than thousands of client connections. What could be the problem any help urgently needed?