PolarDB:Upgrade an instance from Standard Edition to Enterprise Edition

Background

With the rapid development of business, a PolarDB-X Standard Edition instance may face bottlenecks typical of standalone databases such as low query performance on large tables, database overload due to high-concurrency queries, and inadequate capabilities to meet analytical requirements. In these scenarios, scaling up the database does not solve the problem and is also cost-ineffective.

PolarDB-X allows a seamless upgrade of an instance from Standard Edition to Enterprise Edition. The Enterprise Edition resolves the preceding issues of standalone databases by using distributed features and hybrid transaction/analytical processing (HTAP) capabilities and preserves the use experience of a standalone MySQL database.

Prerequisites

• The PolarDB-X Standard Edition instance runs polardb-2.3 _standard_xcluster 5.4.18-20240311 or later.

• The specifications of the PolarDB-X Standard Edition instance must be the same as one of the available specifications of data nodes of the Enterprise Edition.

• The engine version of the PolarDB-X Standard Edition instance must be MySQL 5.7.

Perform a check before an upgrade

1. Log on to the PolarDB-X console.

2. In the top navigation bar, select the region where the instance is deployed.

3. On the Instances page, click the PolarDB-X 2.0 tab.

4. Find the instance from which you want to detach the data disk and click the instance ID.

5. In the Common Operations section, click Upgrade to Enterprise Edition.

6. Before the upgrade, a precheck is required. A temporary instance of the Enterprise Edition is created in the background. The temporary instance and the Standard Edition instance use the same storage node. Click Start Check. The following items are checked.

   Check item	Description	Criterion
   Accounts	Checks whether the accounts can be imported.	The database accounts of the Standard Edition instance can be imported to the temporary Enterprise Edition instance.
   Whitelists	Checks whether the whitelists can be imported.	The whitelists of the Standard Edition instance can be imported to the temporary Enterprise Edition instance.
   eXtended Architecture (XA) transactions	Checks whether XA transactions exist.	An Enterprise Edition instance does not support XA transaction-related statements. The XA RECOVER statement is sent to the Standard Edition instance.
   Number of databases	Checks whether the number of databases exceeds the limit of the Enterprise Edition instance.	The number of databases on the Standard Edition instance does not exceed the logical database limit of the Enterprise Edition instance. If this check item fails, contact technical support.
   Stored procedures or custom functions	Checks whether user-defined stored procedures or custom functions exist.	No user-defined stored procedures or custom functions exist.
   Endpoint	Checks whether only one endpoint exists.	Only one VPC endpoint exists.
   Read-only instances	Checks whether read-only instances exist.	No read-only instances exist.
   Isolation level	Checks whether the isolation level is supported by Enterprise Edition.	The isolation level is supported by Enterprise Edition.

7. Click OK. Then, PolarDB-X initiates a check task for the upgrade of the instance from Standard Edition to Enterprise Edition. You can click the icon in the upper-right corner to view the task progress.

   After the check task is complete, view the check results in the Upgrade to Enterprise Edition dialog box.

Upgrade to Enterprise Edition

1. In the Upgrade to Enterprise dialog box, click Upgrade.

2. On the Upgrade Configuration page, select the specifications and number of compute nodes.

3. Click Buy Now.

4. Click Sign and Purchase.

5. On the Basic Information page of the instance, click the icon in the upper-right corner to open the task list and view the task progress.

6. After the task is in the Metadata Imported state, click Switch over to redirect traffic to the Enterprise Edition instance.

   Important

   The switchover triggers the restart of the instance. During the restart, the service is unavailable for several minutes.

7. Click Clean up. Residual metadata is cleaned to complete the upgrade.

   The instance edition is changed to Enterprise Edition on the Instance List page a few minutes after the upgrade is complete. Click the instance ID to go to the management page of the Enterprise Edition instance.

   Important

   The cleanup operation cleans the resources of the Standard Edition instance. The operation cannot be rolled back.

Usage notes

The following figure shows the upgrade process.

During the upgrade of an instance from Standard Edition to Enterprise Edition, you can view the task status and perform the operations that are described in the following table.

Operation	Description
Switchover	This operation is required to upgrade an instance from Standard Edition to Enterprise Edition. The following tasks are performed in this operation: Switches the DNS connection string to the endpoint of the Enterprise Edition instance to redirect traffic to the Enterprise Edition instance. Switches the data nodes to Enterprise Edition and restarts the data nodes.
Cleanup	Cleans the residual metadata of the Standard Edition instance. This operation is required to upgrade an instance from Standard Edition to Enterprise Edition.
Switchback	Rolls back the switchover. The following tasks are performed in this operation: Switches the DNS connection string to the endpoint of the Standard Edition instance to redirect traffic to the Standard Edition instance. Switches the data nodes to Standard Edition and restarts the data nodes.
Cancel	Terminates the upgrade. The order is refunded.