A RabbitMQ deployment allows for vertical scaling of both the database nodes and its TCP portals.
The vertical scaling option allows for memory and storage to be manually added to each database node. Vertical scaling is the dimension that Compose Auto-scaling operates in.
In the Deployment Resources view for RabbitMQ, the Nodes panel shows the configured database nodes and the memory and storage allocated to the nodes. The rows in the panel display the name, location and IP address of each node.
To add or reduce memory allocated to a RabbitMQ deployment, click Scale. This takes you to the Scale Nodes view:
By adjusting the slider, you can raise or lower the memory allocated to the RabbitMQ nodes. The storage allocation is 1:1 with the selected memory allocation. When the slider is moved, the view updates with the new cost, per month, for the deployment.
Click Confirm to trigger the rescaling of the deployment.
For RabbitMQ there will be at least two TCP portals. Below is an example from the Scale TCP Portals view with the slider set to scale them:
It is possible to add a TCP portal through the Security page, and if you have additional portals they will all be scaled to the new memory size.
If you find you do not need the resources currently provisioned to your deployment you can 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.
Use the Security panel to remove any provisioned TCP/HAProxy portals from your deployment.
If this article didn't solve things, summon a human and get some help.
Updated about a year ago