Redis.Cluster support is broken as of v2.3.6
See original GitHub issueDescription
This change actually caused a breaking change for setups using Redis.Cluster
since uri.options.family
will not be defined when using Redis.Cluster
Doing (uri.options && uri.options.family || uri.options && uri.isCluster)
will work but I haven’t dug into ramifications of doing that.
References
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Redis Cluster implementation is broken · Issue #2328 - GitHub
This issue tracks a resolution to the existing Redis cluster bugs. After they've been fixed, we should reenable Redis cluster tests, which were ......
Read more >redis-py-cluster 2.1.3 - PyPI
This client provides a client for redis cluster that was added in redis 3.0. ... This major version of redis-py-cluster supports redis-py >=3.0.0,...
Read more >Scaling with Redis Cluster
Redis Cluster has support for synchronous writes when absolutely needed, implemented via the WAIT command. This makes losing writes a lot less likely....
Read more >Redis Cluster Support in Redis 2.8.19 - Stack Overflow
Cluster support for Redis is only from v3 - v2.8.19 doesn't do clustering.
Read more >redis-py-cluster Documentation - Read the Docs
If this library supports more then one major version line of redis-py, then the supported python versions must include the set of supported...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jimmy-guzman - this pull request has now been accepted and should be out and live in the next 10 days. Closing this issue.
@jimmy-guzman - thanks and we are working on this fix.