Alibaba Cloud Elasticsearch allows you to upgrade the version or kernel of your Alibaba Cloud Elasticsearch cluster. This ensures that your business is up-to-date. You can upgrade Elasticsearch clusters from V5.6.16 to V6.3.2 or from V6.3.2 to V6.7.0. Upgrades from V5.6.16 to V6.3.2 are unavailable in the Alibaba Cloud Elasticsearch console. If you want to perform such an upgrade, submit a ticket.
Prerequisites
- A precheck is performed for the version upgrade.
For more information about the related check items, see Check items for cluster status and Check for and modify incompatible configurations before you perform an upgrade from V5.6 to V6.3.
- Kernel upgrades: A new kernel version is available.
You can go to the Basic Information page of your cluster to check whether a new kernel version is available for the cluster.
- Upgrades from V5.6.16 to V6.3.2: The configurations of your cluster are modified to
prevent configuration incompatibility. V6.X may be incompatible with some configurations
in V5.X. If these configurations are not modified, the cluster may not provide services
as expected after the upgrade. For more information about the incompatible configurations
and how to modify these configurations, see Check for and modify incompatible configurations before you perform an upgrade from V5.6 to V6.3. For more information about major changes in Elasticsearch V6.X, see Breaking changes in 6.0.
Notice If a client is connected to the cluster whose version you want to upgrade, update the client version before the upgrade. This ensures that the client is compatible with the cluster version after the upgrade. For more information about the version compatibility between clients and clusters, see Compatibility.
Precautions
Restart mode | Principle | Risk and recommendation | Scenario |
---|---|---|---|
Blue-green restart | The system adds nodes of a later version to the cluster, migrates data stored on original nodes to the added nodes, and removes the original nodes from the cluster. |
|
|
Full restart | The system disables all nodes in the cluster and restarts the cluster. | During an upgrade, the system installs a TLS certificate on your cluster. This may interrupt your services but does not cause data loss. Upgrade
duration depends on the specifications of the cluster and the volume of data stored
on the cluster. We recommend that you plan the upgrade in advance.
Note A full restart does not change the IP addresses of the nodes in the cluster. Therefore,
you do not need to update the IP addresses.
|
Upgrades from V5.6.16 to V6.3.2 |
Check items for cluster status
Check item | Normal state |
---|---|
Cluster status | The cluster is in the Active state (indicated by the color green). |
JVM heap memory usage | The JVM heap memory usage of the cluster is less than 75%. |
Disk usage | The disk usage of nodes is less than the value of cluster.routing.allocation.disk.watermark.low. |
Replica shards | All indexes are configured with replica shards. |
Snapshots | The cluster created snapshots during the last hour. |
Custom plug-ins | The cluster does not have custom plug-ins installed. |
ECS instances in the zone where the cluster resides | The zone where the cluster resides has sufficient ECS instances.
Note When you upgrade the version or kernel of a cluster, the system adds nodes of a later
version to the cluster. Then, the system migrates data stored on original nodes to
the added nodes and removes the original nodes from the cluster. Therefore, before
the upgrade, make sure that the zone where the cluster resides has sufficient ECS
instances.
|
YML configuration file | The cluster of a later version is compatible with the YML configuration file in an earlier version. |