Mark Paluch

> Please let me know how to solve this https://github.com/lettuce-io/lettuce-core/issues/2585#issuecomment-1884374064

If you would like us to spend some time helping you to diagnose the problem, please spend some time describing it and, ideally, providing a [minimal sample](https://stackoverflow.com/help/mcve) that reproduces the...

There are a couple questions here, let's try to go about it in sequence: > The question is whether it is expected to have two connections in this case, Lettuce...

Basically, periodic and adaptive refresh strategies are an approximation what typically works although triggers are different. Both do not solve the problem that Redis Cluster doesn't emit notifications upon cluster...

Let's take a step back before jumping right into the code. We default `replOffset` to `-1` to indicate the absence of a replication offset. Lettuce can fetch topology details either...

> querying all nodes in the client initialization. It involves a bit more than that. Clients can reside in loading state at initialization and these nodes would require re-querying. Also,...

That leaves us with the requirement to re-query all cluster nodes and that is what we tried to eliminate in the first place. The main reason I'm reluctant to query...

> What about using the existing connections Existing connections may be busy/blocked so that could cause issues. > Also, as a user-side mitigation, is there a way of getting the...

Lettuce maintains a `Partitions` object that represents all nodes along with their slots. We do select nodes for read and write operations based on that information and we coordinate our...

I'm not quite sure what the difference is. However, I see the following outputs (smaller clusters): # 7.2 ``` 127.0.0.1:7379> cluster nodes 27f88788f03a86296b7d860152f4ae24ee59c8c9 127.0.0.1:7379@17379 myself,master - 0 1696942023000 1 connected...