Hello Fleet. We are running fleet 3.13 with a clustered redis (aws elasticache) of 3 nodes. We've noticed that when pointing Fleet to the cluster alias, all reads and writes end up on a single redis system (the cluster master) with the other 2 idle. Is there a way to split out reads and writes or general redis clustering support in 3.13 or newer versions?
hi! what Juan mentions is correct, we added support for redis cluster in a later version than what you're running, and we've improved how we interact with it over time to make better use of the resources. If you could try out the latest version, that would be the ideal