Ping Xie

Please be patient and stay tuned :) There is a significant amount of groundwork that needs to get done first. We need a strong(er) foundation.

TSC had a discussion on this topic (#361) The rule of thumb is that command error messages should be retained for backward compatibility. Log lines are in general OK to...

> @zuiderkwast Unsure about what you meant by assigning it to Ping for this PR, did you meant it for review or something else ? @hpatro please continue with this...

> Shall we include this in our 7.2.4 release? I think we should try our best to make it happen. It is an important and **fully compatible** fix.

> > Exactly, this issue exists for a new node being added and not related to the upgrade scenario. So, it could happen for any cluster running with hostnames feature....

> if you set all the hostnames at startup a node will never observe a node that doesn't have a hostname. This change introduces a small window where that isn't...

> I think the one open question left is @PingXie concern about using the original client vs a new caching client, so would like to close that before merging. Have...

> > > However, after we finish adding the command reply to reply list and we want to add the length of the reply we optimize using setDeferredReply https://github.com/valkey-io/valkey/blob/unstable/src/networking.c#L762, which...

The announce IPs do not need to be circulated over the cluster bus if you know them a priori and they are also static. I think in the case of...

What is the **end to end** use case here? This proposal seems to suggest that there is a need to retrieve just the members of the sorted set, unordered. What...