Taking advantage of the Redis master/slave replication, adding additional read-only slave nodes to your deployment provides more replication of your data and additional scalability. These read-only nodes allow clients that only need to query the Redis data to access the deployment without impact on the write performance of the primary server.
Each new read-only node comes with an associated portal, and both are added at the same unit scale as the existing nodes and portals on your deployment. The units for the data nodes are 256MB memory and 256MB storage chunks that cost $6.00 per unit. The units of portal scaling are 64MB chunks of memory.
For example, if you have a deployment that currently had nodes sized at 256MB, an additional read-only slave will be added at that size for $6.00, with its portal for $4.50, for a total additional cost of $11.00.
If you have a deployment that has nodes of size 512MB, then an additional read-only slave will be added at that size for $12.00, with its portal for $4.50, for a total additional cost of $16.50.
To add a read-only node go to Deployment Resources and click Add Read-only Slaves in the Nodes panel.
This takes you to the Read-only Slaves view. Each read-only slave will be configured with the same memory and storage as the full Redis nodes. Each read-only slave will also have its own TCP Portal for access. The display shows how many are currently configured.
The slider can be moved to select the number of slaves configured. As the slider is moved, the display updates with the revised cost of the read-only slaves.
Clicking Confirm starts the provisioning of the selected number of Read-only Slaves. Details on how to connect to the new nodes can then be found in the Redis Deployment Overview.
If this article didn't solve things, summon a human and get some help!
Updated about a year ago