Redis Sentinel vs Clustering

Why does the CROSSSLOT Error Occur? This error occurs because the application is trying to run a command on multiple keys, but the keys involved

CLUSTER GETKEYSINSLOT slot count Available since 0 The command returns an array of keys names stored in the contacted node and hashing to the specified

redis crossslot keys in request don''t hash to the same slot Way 1: 1) Node B is importing hash slot 100 is in node A then node B replies with -MOVED to redirect to A point the client to B, and eventually the

redis slot redis:127:in `call': ERR Slot 0 is already busy To do the cleanup, I used: for n in 1 2 3 4 5 6 do redis-cli