This document will describe what must be done when upgrading between different versions to ensure that code still works.
The following exceptions have been changed/added and code that use this client might have to be updated to handle the new classes.
raise RedisClusterException("Too many Cluster redirections") have been changed to raise ClusterError('TTL exhausted.')
ClusterDownException have been replaced with ClusterDownError
Added new AskError exception class.
Added new TryAgainError exception class.
Added new MovedError exception class.
Added new ClusterCrossSlotError exception class.
Added optional max_connections_per_node parameter to ClusterConnectionPool which changes behavior of max_connections so that it applies per-node rather than across the whole cluster. The new feature is opt-in, and the existing default behavior is unchanged. Users are recommended to opt-in as the feature fixes two important problems. First is that some nodes could be starved for connections after max_connections is used up by connecting to other nodes. Second is that the asymmetric number of connections across nodes makes it challenging to configure file descriptor and redis max client settings.
In 0.3.0 release the name of the client class was changed from RedisCluster to StrictRedisCluster and a new implementation of RedisCluster was added that is based on redis.Redis class. This was done to enable implementation a cluster enabled version of redis.Redis class.
Because of this all imports and usage of RedisCluster must be changed to StrictRedisCluster so that existing code will remain working. If this is not done some issues could arise in existing code.
No major changes was done.