There are several reasons why you might want to change the configuration of your deployment:
- To add features, such as machine learning or APM (application performance monitoring).
- To increase or decrease capacity by changing the amount of reserved memory and storage for different parts of your deployment.
- To enable high availability by adjusting the number of data centers that parts of your deployment run on.
- To upgrade to new versions of Elasticsearch. You can upgrade from one major version to another, such as from 6.7.1 to 7.0.0, or from one minor version to another, such as 6.1 to 6.2. You can’t downgrade versions.
- To change what plugins are available on your Elasticsearch cluster.
You can change the configuration of a running deployment from the Configuration pane in the Elasticsearch Service Console.
With the exception of major version upgrades for Elastic Stack products, Elasticsearch Service can perform configuration changes without having to interrupt your deployment. You can continue searching and indexing. The changes can also be done in bulk: in one action, you can add more memory, upgrade, adjust the number of Elasticsearch plugins and adjust the number of availability zones, for example.
We perform all of these changes by creating instances with the new configurations that join your existing deployment before removing the old ones. For example: if you are changing your Elasticsearch cluster configuration, we create new Elasticsearch nodes, recover your indexes, and start routing requests to the new nodes. Only when all new Elasticsearch nodes are ready, do we bring down the old ones.
By doing it this way, we reduce the risk of making configuration changes. If any of the new instances have a problems, the old ones are still there, processing requests.
If you use a Platform-as-a-Service provider like Heroku, the administration console is slightly different and does not allow you to make changes that will affect the price. That must be done in the platform provider’s add-on system. You can still do things like change Elasticsearch version or plugins.
To change the Elasticsearch cluster in your deployment:
- Log into the Elasticsearch Service Console.
On the Deployments page, select your deployment.
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
- From your deployment menu, select Elasticsearch and then Edit.
Let the user interface guide you through the cluster configuration for your cluster. For a full list of the settings that we support, see What Deployment Settings Are Available?.
If you are changing an existing deployment, you can make multiple changes to your Elasticsearch cluster with a single configuration update, such as changing the capacity and upgrading to a new Elasticsearch version in one step.
- Save your changes. The new configuration takes a few moments to create.
You can review the changes to your configuration on the Activity page, with a tab for Elasticsearch and one for Kibana.