It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.

The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Change your deployment configuration Add plugins »
Elastic Docs ›Elastic Cloud Enterprise Reference [2.12] ›Administering deployments ›Change your deployment configuration

Resize your deployment

edit

Resize your deployment

edit

Elasticsearch scales to whatever capacity you need and with as many nodes as the available resources can support. If you don’t have enough available resources, add some capacity first.

You can also enable autoscaling on a deployment to have the available resources for components, such as data tiers and machine learning nodes, adjust automatically as the demands on the deployment change over time. See Deployment autoscaling to learn more.

To resize a deployment:

  1. Log into the Cloud UI.

  2. On the Deployments page, select your deployment.

    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.

  3. From your deployment menu, go to the Edit page.

  4. Change the deployment configuration:

    Fault tolerance

    If the initial deployment you created uses only one availability zone, it is not fault tolerant. On a production system, enable high availability by changing your deployment to use at least two availability zones, three for mission-critical deployments. The number of instances comes from the number of zones and the type of template. Having more nodes or instances lets you scale out horizontally by adding more processing capacity to your deployment.

    Deployments that use only one availability zone are not highly available and are at risk of data loss, if you do not configure an external snapshot repository to enable regular backups. To safeguard against data loss, you must use at least two data centers and configure an external repository for backups.

    RAM per instance

    Node and instance capacity should be sufficient to sustain your search workload, even if you lose an availability zone. Currently, half of the memory is assigned to the JVM heap. For example, on an Elasticsearch cluster node with 32 GB RAM, 16 GB would be allotted to heap. Up to 64 GB RAM and 1 TB storage per node are supported.

    A summary of your sections for each instance and the entire deployment are available for you to review before finalizing your changes.

  5. Click Save changes.

Example: From very small to very large

edit

This example shows you how to change an existing, very basic deployment to use high availability and to add capacity.

To scale your deployment from very small to very large:

  1. Log into the Cloud UI.

  2. On the Deployments page, select your deployment.

    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.

  3. From your deployment menu, go to the Edit page.
  4. Under Fault tolerance, select 3 zones for mission critical environments*.
  5. Under RAM per instance, select 64 GB memory / 2 TB storage.
  6. Click Save changes.

There is no downtime when adding high availability. Deployments with high availability will continue to handle user requests, even if the configuration changes are applied.

« Change your deployment configuration Add plugins »