A Redis deployment allows for vertical and horizontal scaling:
The vertical scaling option allows for memory to be manually added to each database node. Vertical scaling is the dimension that Compose Auto-scaling operates in. If the Redis database is not in Cache mode the auto-scaling system will increase the available memory when under memory pressure. When in Cache mode, the auto-scaling will not operate and the user must select the amount of memory they need for their Redis database.
The horizontal scaling option allows for read-only nodes, each with their own access portal, to be added to the deployment. Details and instructions for adding and utilizing additional data nodes can be found on the Horizontal Scaling for Redis page.
You can add additional TCP portals and SSH portals to your deployment through the Security page of the Compose UI. Also, any TCP or SSH portals can also be scaled with additional memory resources.
In the Deployment Resources view for Redis, the Nodes panel shows the database nodes configured. Each row displays the node name, it's location and its IP address. In the top right, the memory and storage allocated to the nodes is displayed.
The Deployment Resources panel.
In the lower right of the panel are buttons to adjust the nodes. To add (or reduce) memory allocated to a Redis deployment, click Scale. This takes you to the Scale Nodes view:
The Scale Nodes panel.
By adjusting the slider, you can raise or lower the memory allocated to the Redis nodes. The storage allocation is 1:1 with the selected memory allocation. When the slider is moved, the view will update with the new cost, per month, for the deployment.
Scaling nodes dialogue.
Clicking Confirm triggers the rescaling of the deployment.
For Redis, there will be at least one TCP portal, zero or more SSH portals and as many Read-only Slave portals as there are Read-only Slaves. The screenshot below shows an example from the Deployment Resources view where one of each is configured:
Listing of portals on the Deployment Resources panel.
Each class of portal has its own panel, with Scale button and displays. Clicking Scale for any of them will display another slider for the memory allocated to all portals in that class and allow you to see the costs involved in that scaling change. Clicking Confirm on the slider will make that scaling change. Portal scaling should be carried out in conjunction with horizontal and vertical database scaling.
To add either a TCP portal or a SSH portal to your Redis deployment, navigate to the Security page in the Compose UI.
The Security page.
You may add an SSL/TLS enabled TCP portal backed by a Let's Encrypt certificate by checking the SSL Enabled? box.
Clicking either Add TCP portal or Add SSH portal brings up a dialog, detailing the cost of each additional portal. Click Create to add the portal to your deployment. The new connection information will appear in the Deployment Overview.
If you find you do not need the resources currently provisioned to your deployment you can manually scale down the deployment. Compose auto-scaling will NOT automatically scale down or remove resources that you are not currently using.
Scaling down works similarly to scaling up. Moving the sliders to the left shows the difference in the cost, and the new monthly total.
In the Security panel it is possible to remove any provisioned TCP portals or SSH portals from your deployment. At least one TCP portal will be required on the deployment.
To remove any read-only nodes from a deployment, please contact support.
If this article didn't solve things, summon a human and get some help!