MOVED redirection loop detected with AWS Elasticache redis
See original GitHub issueGetting following error:
org.redisson.client.RedisException: MOVED redirection loop detected. Node redis://xxxxx-cache-0001-001.xxxxx-cache.yyyyy.usw2.cache.amazonaws.com:6379 has further redirect to redis://xxxxx-cache-0001-001.xxxxx-cache.yyyyy.usw2.cache.amazonaws.com:6379
We are using redisson 3.13.4 ( tried with 3.13.6 also) with AWS Elasticache Redis. For our internal testing we created AWS Elasticache Redis cluster with following configuration: Shards: 1 replica: 1 Engine compatibilty: 5.0.6 readMode=MASTER.
Connecting to configuration endpoind. In the error you see ‘redis://’ but we are using ‘rediss://’ , there is another bug in RedisException where ‘redis://’ ( without extra ‘s’) is hardcoded.
It was working fine till last week.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Learn why Redis client read requests are read from or ...
I'm using Amazon ElastiCache for Redis. Why are my Redis client read requests always read from or redirected to the primary node of...
Read more >ReplyError: MOVED error after connecting to Redis Cluster AWS
The MOVED error is caused by using the Redis client directly and the configuration endpoint of ElastiCache (Redis Cluster Mode).
Read more >Best practices: Redis clients and Amazon ElastiCache for Redis
In this post, we cover best practices for interacting with Amazon ElastiCache for Redis resources with commonly used open-source Redis ...
Read more >Scaling with Redis Cluster
This makes it easy to add and remove cluster nodes. For example, if I want to add a new node D, I need...
Read more >Connect to the cluster's node - Amazon ElastiCache for Redis
Log in to an Amazon EC2 instance and connect to a node in the cache cluster. ... If redirection isn't enabled, the command...
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
After further investigation, we found that problem was in our configuration. We have support for both clustered and non clustered mode. Configuration which causes the switch was changed incorrectly, because of which AWS Elasticache redis cluster configuration endpoint was getting used with ‘ReplicatedServersConfig’ instead of ‘ClusterServersConfig’.
Good thing I guess is, through this ticket, ‘redis’ vs ‘rediss’ scheme related issue got fixed.
Thanks for your help, appreciate quick responses on this ticket.
Could you share log with logging level = ‘TRACE’ for
org.redisson
package?