Representing Amazon ElasticCache (no cluster)
See original GitHub issueI have AWS ElasticCache Redis (no cluster) with replications. I have an application that needs to connect only to slaves for reads and scale reads across the multiple slaves. I read through your API and it seems to me that I should list all slaves as sentinels and specify role as slave? I couldn’t figure out how to scale reads across slaves; is this supported?
var redis = new Redis({
sentinels: [{ host: '127.0.0.1', port: 26379 }, { host: '127.0.0.1', port: 26380 }],
name: 'mymaster',
role: 'slave',
readOnly: true
});
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Replication: Redis (Cluster Mode Disabled) vs. Redis (Cluster ...
A Redis (cluster mode disabled) cluster always has a single shard (API/CLI: ... If you have no replicas and the node fails, you...
Read more >Amazon Elasticache FAQs - Amazon Web Service
You can choose to configure a 500-node cluster that ranges between 83 shards (one master and five replicas per shard) and 500 shards...
Read more >How to work with Cluster Mode on Amazon ElastiCache for ...
Open the AWS Management Console in your favorite browser and navigate to ElastiCache. Click the blue “Create” button towards the middle of the ......
Read more >Monitoring best practices with Amazon ElastiCache for Redis ...
This post shows you how to maintain a healthy Redis cluster and prevent disruption using Amazon CloudWatch and other external tools.
Read more >Auto Scaling ElastiCache for Redis clusters
Auto Scaling in ElastiCache for Redis is not supported for clusters running in Global datastores, Outposts or Local Zones. AWS Auto Scaling for...
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
No, there’s no built-in way for this. However, it’s possible for you to create multiple connections to your replication (each for a slave), and route the queries to random connections. For example:
That is a really good alternative… thanks for the suggestion!
I would close this issue