AWS Redis Cluster fails with CONFIG (already set skip_full_coverage_check=False)
See original GitHub issueThe same issue still happens:
from rediscluster import StrictRedisCluster
startup_nodes = [{"host": "xxxx.clustercfg.apn2.cache.amazonaws.com", "port": "6379"}]
r = StrictRedisCluster(startup_nodes=startup_nodes, decode_responses=True, skip_full_coverage_check=False)
r.set('foo', 'bar')
value = r.get('foo')
Exception:
Traceback (most recent call last):
File "testRedisCluster.py", line 11, in
r = StrictRedisCluster(startup_nodes=startup_nodes, decode_responses=True, skip_full_coverage_check=False)
File "/Library/Python/2.7/site-packages/rediscluster/client.py", line 181, in init
**kwargs
File "/Library/Python/2.7/site-packages/rediscluster/connection.py", line 141, in init
self.nodes.initialize()
File "/Library/Python/2.7/site-packages/rediscluster/nodemanager.py", line 228, in initialize
need_full_slots_coverage = self.cluster_require_full_coverage(nodes_cache)
File "/Library/Python/2.7/site-packages/rediscluster/nodemanager.py", line 270, in cluster_require_full_coverage
return any(node_require_full_coverage(node) for node in nodes.values())
File "/Library/Python/2.7/site-packages/rediscluster/nodemanager.py", line 270, in
return any(node_require_full_coverage(node) for node in nodes.values())
File "/Library/Python/2.7/site-packages/rediscluster/nodemanager.py", line 267, in node_require_full_coverage
return "yes" in r_node.config_get("cluster-require-full-coverage").values()
File "/Library/Python/2.7/site-packages/redis/client.py", line 715, in config_get
return self.execute_command('CONFIG GET', pattern)
File "/Library/Python/2.7/site-packages/redis/client.py", line 668, in execute_command
return self.parse_response(connection, command_name, **options)
File "/Library/Python/2.7/site-packages/redis/client.py", line 680, in parse_response
response = connection.read_response()
File "/Library/Python/2.7/site-packages/redis/connection.py", line 629, in read_response
raise response
redis.exceptions.ResponseError: unknown command 'CONFIG'
I’m using redis-py-cluster 1.3.4.
Any idea?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Troubleshoot connecting to an ElastiCache for Redis cluster
Connectivity issues can have multiple root causes. The most common issues are: The cluster isn't ready. The cluster is unhealthy. The network ...
Read more >Troubleshooting - Amazon ElastiCache for Redis
If clients and the ElastiCache cluster are in different subnets, make sure that their route tables allow them to reach each other. More...
Read more >Amazon ElastiCache error messages - AWS Documentation
Solution: Change your request so that the cluster does not have more than %n nodes. Or, if you need more than %n nodes,...
Read more >Troubleshoot changing an ElastiCache Redis node type
The following are common reasons for problems changing your Redis node type: Insufficient memory on the target node type.
Read more >Mitigating Failures - Amazon ElastiCache for Redis
When running the Redis engine, you have the following options for minimizing the impact of a node or Availability Zone failure.
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 Free
Top 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

Oh, Yes. Set to True works now. Thanks!
@mingtm The solution to your problem there is that you are not running through the redis-cluster client class but throught the normal redis-py class and it can’t handle the MOVED case properly. I would suggest your have some installation error or some configuration error but if you fix your code it should start to work again properly.