Upgrading an Exclusive Microservice Engine

Exclusive microservice engines are created using the latest engine version. When a later version is released, you can upgrade your microservice engine.

Only exclusive microservice engines can be upgraded. Version rollback is not supported after the upgrade.

Context

During the upgrade, the performance of HA engines is different from that of non-HA engines.

For HA engines, two instances are upgraded in rolling mode without service interruptions. However, one of the two access addresses may be unavailable. In this case, you need to quickly switch to the other instance. Currently, ServiceComb SDK, Go chassis, and Mesher support instance switching. If you call the APIs of the service center and configuration center for service registry and discovery, instance switching is required.
A non-HA engine has only one service instance. During the upgrade, services are interrupted and cannot be registered, discovered, or modified. Therefore, you need to evaluate whether the service is affected during an upgrade. The reliability of ServiceComb SDK, Go chassis, and Mesher is enhanced. During service interruption, the client caches data. If an empty instance is found, the client uses the local cache. If you call the APIs of the service center and configuration center for service registry and discovery, you need to use cache.

Procedure

Log in to ServiceStage and choose Infrastructure > Cloud Service Engines.
Select an available microservice engine that can be upgraded, click , and choose Upgrade.

You can also click the target microservice engine and click Upgrade in the upper right corner of the details page.
Select the target version and view the version description.
Click OK.

If the upgrade fails, click and choose Retry.