This will describe all changes that StrictRedisCluster have done to make a command to work in a cluster environment.
If a command is not listed here then the default implementation from StrictRedis in the redis-py library is used.
The following commands will send the same request to all nodes in the cluster. Results is returned as a dict with k,v pair (NodeID, Result).
This command will send the same request to all nodes in the cluster in sequence. Results is appended to a unified list.
The following commands will only be send to the master nodes in the cluster. Results is returned as a dict with k,v pair (NodeID, Command-Result).
This command will sent to a random node in the cluster.
The following commands will be sent to the server that matches the first key.
This following commands will be sent to the master nodes in the cluster.
- script load - the result is the hash of loaded script
- script flush - the result is True if the command succeeds on all master nodes, else False
- script exists - the result is an array of booleans. An entry is True only if the script exists on all the master nodes.
The following commands will be sent to the sever that matches the specefied key.
The following commands is blocked from use.
Either because they do not work, there is no working implementation or it is not good to use them within a cluster.
- bitop - Currently to hard to implement a solution in python space
- client_setname - Not yet implemented
- move - It is not possible to move a key from one db to another in cluster mode
- script_kill - Not yet implemented
- slaveof - Cluster management should be done via redis-trib.rb manually
- unwatch - Not yet implemented
- watch - Not yet implemented
The following methods is overridden from StrictRedis with a custom implementation.
They can operate on keys that exists in different hashslots and require a client side implementation to work.