@dustinrue Okay, I think this might be a misunderstanding of what's going on. Dragonfly uses the same protocol and clients as Valkey.Your client application (whatever it might be) is using the protocol to direct to different parts of the cluster.
-
@dustinrue Okay, I think this might be a misunderstanding of what's going on.
Dragonfly uses the same protocol and clients as Valkey.
Your client application (whatever it might be) is using the protocol to direct to different parts of the cluster. -
@linux_mclinuxface I don't *think* it is because the config on my side is only aware that is connected to Redis at all, it has no idea it is a cluster, sentinel system or otherwise. Maybe I need to dig more
-
@dustinrue curious what you find.
As far as I can figure, Dragonfly works like any cluster on the protocol level, which means it’s either throwing MOVED errors when you try to access data on another shard or you client is directing the topology.
There are active/active variants of Redis but there they are either expensive and require special care and use (CRDTs) or they drop data (KeyDB). Either way, you’d know it and they would definitely be taking about in docs!