Upgrade Example for a Fixed Version Number on the Consumer Side

Assumed Background

When a consumer accesses a service, the version number is fixed. For example, if the consumer wants to access the 0.1.0 version of the /oneservice/customers service instead of the * version, the version policy cannot be used for upgrade. In this case, you can deploy a new implementation of the same version of the same service, disable the old instance, and delete the old instance to complete the service upgrade. This method is equivalent to replacing the service implementation and cannot change the service version.

Prerequisites

Container nodes where old implementation instances are not deployed are available. Do not deploy new implementation instances on the same node as old ones. Otherwise, when an instance is disabled, the new and old instances cannot be distinguished, and the system cannot determine whether the new instance starts working or the old instance stops working through the monitoring data. If no idle container is available, you can disable some old implementation instances and delete them after they do not process requests.

Procedure

1. Deploy a new instance by referring to Adding a BLU Instance and ensure that the newly implemented instance starts to process requests properly.
2. Log in to FusionInsight Manager.
3. Choose Cluster > Services > Containers, and click the SGP Manager tab.
4. In the list box on the left, click App Service List.
5. In the list on the right, click the name of the desired service in the Name column.
6. Confirm that the new instance starts to process requests properly.
   

   On the State page, if the new instance starts to report monitoring data, the new instance starts to process requests properly.

7. Click the Providers tab, select the old instance to be disabled, and click Disable. In the displayed dialog box, click OK.
8. Delete the BLU corresponding to the old instance by referring to Adding a BLU Instance.
   

   You can delete an old instance only after confirming that the old instance does not process requests. To determine whether an old instance does not process requests, check the instance run log or check whether the monitoring data volume of the old instance node does not increase.

Important Notes

This method is not recommended because the version number of the service upgraded in this way cannot be updated. From the management perspective, you cannot determine whether the service is new or old. In addition, you need to check background logs to determine whether the new or old instance is working based on the monitoring data. This method is invalid when the new and old instances share the same node, and the upgrade is inconvenient.