After you create a Global Database Network (GDN), you can create new clusters and add them to the GDN as secondary clusters. If they are no longer needed, you can remove them from the GDN. A removed secondary cluster can still be used as a standalone PolarDB cluster.
Applicability
Before adding a secondary cluster, you must first create a global database network.
Supported regions
GDN is available in more than 10 regions worldwide, including the Chinese mainland, China (Hong Kong), and other regions outside the Chinese mainland.
Primary Cluster Region | Secondary Cluster Region |
All regions in the Chinese mainland | In the same region as the primary cluster or in a region in the Chinese mainland other than the region where the primary cluster is located. The same region as the primary cluster, or any other region in the Chinese mainland. For example, if the primary cluster is in China (Hangzhou), the secondary cluster can be in China (Hangzhou) or any other region in the Chinese mainland. Note If you have other region requirements, submit a ticket to contact us. |
Regions outside the Chinese mainland | China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Philippines (Manila), Thailand (Bangkok), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and UK (London). |
For regions outside the Chinese mainland, you must sign the Cross-Border Data Transfer Compliance Agreement before you create a secondary cluster.
Feature limits
Clusters in a GDN do not support the serverless feature or In-Memory Column Index (IMCI).
Clusters in a GDN do not support the database and table restoration feature.
Other limits
A GDN can consist of one primary cluster and up to four secondary clusters.
The primary cluster and secondary clusters must have the same database engine version: PostgreSQL 14.
The node specifications of a secondary cluster must be greater than or equal to those of the primary cluster. We recommend that you keep the specifications consistent.
A cluster can belong to only one GDN.
Add a secondary cluster
Log on to the PolarDB console. In the navigation pane on the left, click Global Database Network (GDN).
On the Global Database Network (GDN) page, find the target GDN and click Add Secondary Cluster in the Actions column.
On the purchase page that appears, set the following parameters. Configure other parameters as needed. For more information, see Custom purchase.
Region: Select a region. For information about supported regions, see Prerequisites.
Creation Method: Select Create Secondary Cluster.
Global Database Network: Select the GDN to which you want to add the cluster. The GDN that you selected in the previous step is selected by default.
Database Engine: The database engine version must be the same as that of the primary cluster: PostgreSQL 14 .
Compute Node Specifications: The compute node specifications of the secondary cluster must be the same as those of the primary cluster. If you require higher specifications for the secondary cluster, you can upgrade its specifications on the cluster details page after it is created.
After you complete the purchase, return to the Global Database Network (GDN) page. Find the target GDN and click its Global Database Network ID to open the GDN details page. The new secondary cluster is displayed in the Clusters section.
Remove a secondary cluster
Log on to the PolarDB console. In the navigation pane on the left, click Global Database Network (GDN).
On the Global Database Network (GDN) page, find the target GDN and click its Global Database Network ID to open the GDN details page.
In the Clusters section, find the target secondary cluster and click Remove in the Actions column.
NoteThe removal process takes about 5 minutes.
During the removal process, the endpoints of all clusters in the GDN, including the secondary cluster that is being removed, remain available. You can continue to access the databases using the cluster endpoints.
Only secondary clusters can be removed from a GDN. The primary cluster cannot be removed.
After a secondary cluster is removed from a GDN, data synchronization between the secondary cluster and the primary cluster stops. The system then sets the cluster to read/write mode.
After a cluster is removed from a GDN, it cannot be added back to a GDN as a secondary cluster. Proceed with caution.
In the dialog box that appears, carefully read the notes, and then click OK.
Switch the primary cluster
Log on to the PolarDB console. In the navigation pane on the left, click Global Database Network (GDN).
On the Global Database Network (GDN) page, find the target GDN and click its Global Database Network ID to open the GDN details page.
In the Clusters section, find the target secondary cluster and click Switch To Primary Cluster in the Actions column.
In the Primary/Secondary Switchover dialog box, select the secondary cluster that you want to specify as the new primary cluster, and then click OK.
NoteThe Forced Switchover feature is not supported.
If the original primary cluster in the GDN has an Internet endpoint, make sure that the new primary cluster also has an Internet endpoint. Otherwise, your application may fail to access the database. For more information, see View or apply for an endpoint.
Switching the primary cluster may cause a transient connection break that lasts for about 160 seconds. We recommend that you perform this operation during off-peak hours and make sure that your application has an automatic reconnection mechanism.
References
Global Database Network (GDN). Learn about GDN, its service architecture, and common scenarios.
Connect to a GDN. Learn how to connect to a global database network (GDN).
Related API operations
API | Description |
Use the CreateDBCluster operation to add a secondary cluster to a GDN. The following parameters are required:
| |
Remove a secondary cluster from a GDN. | |
Switch the primary cluster of a GDN. |