The vertical scaling option allows for memory and storage to be manually added to each database node. Vertical scaling is also the dimension that Compose Auto-scaling operates in.
If you are using Elasticsearch 2.4.2 and above you can take advantage of horizontal scaling by adding data-nodes to your deployment. Details and instructions for adding and utilizing additional data nodes can be found on the Horizontal Scaling for Elasticsearch page.
All versions of Elasticsearch support adding TCP portals and SSH tunnels to a deployment through the Security panel of the Compose UI.
In the Deployment Resources view for Elasticsearch, the Nodes panel shows the configured database nodes. Each row displays the node name, location, and IP address. In the top right, the memory and storage allocated to the nodes is displayed.
In the lower right of the Nodes panel you'll find buttons to adjust the nodes. To add or reduce memory allocated to an Elasticsearch deployment, click Scale. This takes you to the Scale Nodes view:
By adjusting the slider, you can raise or lower the storage allocated to the Elasticsearch nodes. The memory allocation is 10:1 with the selected memory allocation. When the slider is moved, the view updates with the new cost per month for the deployment.
Clicking Confirm triggers the rescaling and a rolling restart of your deployment.
An Elasticsearch deployment contains at least two TCP portals and zero or more SSH portals. If you wish to scale either portal type with more memory, click Scale, which brings you to a page with a slider. This is the Scale TCP Portals view:
The Scale SSH Portal view is similar. If more than one SSH portal is configured for the deployment, both with be scaled to the new memory size.
To add an SSH or TCP portal to your deployment, navigate to the Security panel in the Compose UI.
In the SSH portals section click Add SSH portal and a confirmation pops up to confirm that you would like to add an SSH portal for an additional $4.50/month. Click Confirm to provision the portal.
Adding a TCP portal is the same; they are also billed at an additional $4.50/month.
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 or SSH portals from your deployment.
It is not possible to restore a TCP/haproxy portal once it has been removed from your deployment.
To remove any data nodes from an Enterprise deployment, please contact support.
If this article didn't solve things, summon a human and get some help.
Updated about a year ago