REDIS Cluster Support

sirTangale, I have not heard of that being a limitation. Do you find it documented somewhere?

My understanding is that the ability of the redis client to handle a "moved" response from redis is a built-in feature of the jedis library cf uses. I've not explored what jedis version adds that support, and different cf versions can have different jedis versions--perhaps updated in a cf uodate, in fact.

But Kane refers to being on cf 2016. Kane, are you really still stuck on that, which last got any updates (including security updates) in 2021? That's a grave risk. Then also you could run into such issues6  with the old libraries it includes.

I've not yet tried myself to connect cf sessions to a Redis configured as a cluster, and I'd like to try it just to be sure. 

But until then, Kane, here's another idea to consider: do a test of a cf page that you open in a new incognito/private window in your browser (or clear all your cookies). I'm wondering if cf may handle things better when it creates a NEW session and then redis implements that in its cluster member. That may cause it to better track where it is, thus preventing the MOVE operation. That's just a guess.

Finally, what is the version of the REDIS server you're connecting to? That may also have a bearing on things here.