As your business develops, you may have higher requirements for the configuration of your Elasticsearch cluster. If the current configuration of your Elasticsearch cluster cannot meet your business requirements, you can upgrade the configuration. This topic describes how to upgrade the configuration of an Elasticsearch cluster and the related precautions.
- Evaluate the specifications and storage capacity of your cluster.
For more information, see Evaluate specifications and storage capacity.
- Log on to the Kibana console and check whether your cluster stores indexes in the close state. If your cluster
stores such indexes, you must open the indexes. Otherwise, the upgrade fails.
- Run the following command to view the statuses of indexes:
- Run the following command to open an index in the close state:
Replace <index_name> with the name of the index in the close state.
- Run the following command to view the statuses of indexes:
|Impact on services||
|Changes in billing||
After you submit a configuration upgrade order, your cluster is charged based on the new configuration. For more information about billing rules, see Pay-as-you-go and Subscription.
Note During a configuration upgrade, you can check the price of your order on the Upgrade/Downgrade page in real time.
|Version upgrades||You cannot upgrade the version of your cluster during a configuration upgrade. For
more information, see Upgrade the version of a cluster.
|Updates of disk types||
Disks with low storage performance can be updated to disks with high storage performance. The following types of disks are listed in ascending order of their storage performance: ultra disks, standard SSDs, and enhanced SSDs (ESSDs). You can update the disk types of nodes in your cluster based on your business requirements. For more information about disks, see Disks.
Note You cannot update SSDs to ESSDs at performance level 0.
|Resource insufficiency in the zone where your cluster resides||If the zone where your cluster resides has insufficient resources for a configuration upgrade, you can migrate the nodes in the zone to another before the upgrade. For more information, see Migrate nodes in a zone.|
|Shard allocation||If you change the number of nodes in your cluster during a configuration upgrade, the system does not reallocate shards to the nodes in the cluster. This may lead to unbalanced loads on the nodes. For more information about the analysis for and solutions to unbalanced loads on nodes, see Unbalanced loads on a cluster.|
- Log on to the Elasticsearch console.
- In the left-side navigation pane, click Elasticsearch Clusters.
- In the top navigation bar, select the resource group to which your cluster belongs and the region where your cluster resides. In the left-side navigation pane, click Elasticsearch Clusters again.
- On the Elasticsearch Clusters page, find the cluster and click Upgrade Configuration in the Actions column.
- On the Upgrade/Downgrade page, change the configuration of the cluster.
You can change node specifications, storage types, or storage space per node.
The Current Config section of the Upgrade/Downgrade page shows the current configuration of the cluster. You can use this as a reference during the upgrade.
Follow the instructions on the Upgrade/Downgrade page to upgrade the configuration of your cluster based on your business requirements. For more information about the parameters on the page, see Parameters on the buy page. The following table describes only some of the parameters.
Parameter Description Data Node The maximum storage space supported by a single data node varies based on the disk type of the node. You can check specific limits in the Elasticsearch console.Notice
- If the value of Data Node Disk Type in the Current Config section is Ultra Disk and your cluster is in an abnormal state (indicated by the color yellow or red), you cannot increase the value of Data Node Storage Space to a value greater than 2,048. If you want to increase the value of Data Node Storage Space to a value greater than 2,048, you must make sure that your cluster is in a normal state before the upgrade. Alternatively, you can increase the number of data nodes during the upgrade.
- Data nodes with 1 vCPU and 2 GiB of memory are designed only for testing purposes. Do not use such data nodes for production purposes. The service level agreement (SLA) does not apply to such data nodes. Therefore, we recommend that you upgrade your data nodes with 1 vCPU and 2 GiB of memory at the earliest opportunity.
Dedicated Master Node You can purchase or upgrade dedicated master nodes. Warm Node You can purchase or upgrade warm nodes. Client Node You can purchase or upgrade client nodes. Kibana Node You can upgrade your Kibana node.Notice When you purchase an Elasticsearch cluster, Alibaba Cloud provides a Kibana node for you free of charge. This Kibana node offers 1 vCPU and 2 GiB of memory. You can upgrade the Kibana node on the Upgrade/Downgrade page. Forced Update If your cluster is in an abnormal state (indicated by the color red or yellow) and your services are severely affected, you must immediately upgrade the configuration of the cluster. In this case, we recommend that you select Forced Update. The system will perform a forced update regardless of the cluster status. The update requires only a short period.Notice
- After the forced update, the system restarts your cluster. During the restart, the services running on the cluster may be unstable.
- If you do not select Forced Update, the system uses the default mode to restart your cluster to make the changes take effect. For more information, see Restart a cluster or node.
Intelligent Update The Intelligent Update feature is enabled by default. When the Intelligent Update feature is enabled, the system selects an appropriate method based on the modified items to update the configuration of your cluster. You can disable the Intelligent Update feature. After this feature is disabled, you can select an update mode based on your business requirements. The following modes are supported:
- Blue-green Update: The system adds the same number of nodes to your cluster, seamlessly migrates data from the original nodes to the new nodes, and removes the original nodes from the cluster. This process is seamless but time-consuming, and the IP addresses of nodes are changed. If you have specified the IP addresses of the nodes in the configuration file of the cluster, you must update the IP addresses of the nodes in the configuration file at the earliest opportunity after the upgrade.
- In-place Update: The system performs a rolling update for the nodes that you want to update. This process does not involve data migration, and the time that is required for this process is not affected by the data volume of your cluster. However, the performance of your cluster may be affected.
For more information, see Cluster update methods.Notice If you do not have special requirements for your business, we recommend that you enable the Intelligent Update feature.
- Read the terms of service, select Elasticsearch Terms of Service, and then click Buy Now. After you complete the payment, the system restarts the cluster to make the changes take effect.
- Can I upgrade or downgrade the version of an Elasticsearch cluster?
- Can I change the cloud disk type of an Elasticsearch cluster?
- Does the system reallocate shards for nodes in an Elasticsearch cluster after the number of nodes in the cluster is changed?
- Are services affected when I modify the configuration of an Elasticsearch cluster?
- When I purchase an Elasticsearch cluster, I performed an incorrect configuration. How do I modify the configuration after the cluster is created?
- Can I downgrade the configuration of an Elasticsearch cluster? If yes, what do I do?
- Why do I need to upgrade the data nodes with the specifications of 1 vCPU and 2 GiB of memory in Elasticsearch clusters?
- How do I modify the configuration of an Elasticsearch cluster to ensure that services run as expected when a temporary business surge occurs?
- When I upgrade the configuration of an Elasticsearch cluster, the system displays the following error message: UpgradeVersionMustFromConsole. What do I do?
- When am I allowed to forcefully restart an Elasticsearch cluster? What is the impact of a force restart?
- What do I do if an error is reported when I upgrade the configuration of an Elasticsearch cluster or when a configuration upgrade for an Elasticsearch cluster times out?
- Will the existing data in an Elasticsearch cluster be lost if I change the cloud disk type of the cluster?
- When I upgrade the configuration of an Elasticsearch cluster, the system displays a prompt message indicating that the cluster is in an unhealthy state, but the cluster is in a normal state indicated by the color green. What do I do?
- Can I upgrade the vCPU configurations of an Elasticsearch cluster without migrating data?
API operation for upgrading the configuration of a cluster: UpdateInstance