PolarDB:Create a GDN

Limits

• A cluster in a GDN must be of Enterprise Edition and meet the following requirements:

  • A PolarDB for MySQL 8.0.2 cluster

  • A PolarDB for MySQL 8.0.1 cluster whose revision version is 8.0.1.1.17 or later.

  • A PolarDB for MySQL 5.7 cluster whose revision version is 5.7.1.0.21 or later.

  • A PolarDB for MySQL 5.6 cluster whose revision version is 5.6.1.0.32 or later.

• The primary cluster and secondary clusters must have the same database engine version, which can be MySQL 8.0, MySQL 5.7, or MySQL 5.6.

• A GDN consists of one primary cluster and up to four secondary clusters. For more information about limits on their regions, see Region mappings between the primary and secondary clusters.

  Note

  To add more secondary clusters, go to Quota Center. Click Apply in the Actions column corresponding to GDN cluster upper limit adjustment.

• A cluster belongs to only one GDN.

• A secondary cluster in the GDN must have at least 4 cores.

• Clusters in the GDN do not support the database and table restoration feature.

Usage notes

You must sign the PolarDB Cross-border Data Transfer Compliance Commitment if you plan to create a secondary cluster in a region outside the Chinese mainland for a GDN.

• The following table lists the region mappings between the primary and secondary clusters in a GDN.

  Region of primary cluster	Region of secondary cluster
  All regions in Chinese mainland	In the same region as the primary cluster or in a region in Chinese mainland other than the region where the primary cluster is deployed. For example, if the primary cluster is in the China (Hangzhou) region, secondary clusters can be in the China (Hangzhou) region or another region in Chinese mainland.
  China (Hong Kong) and regions outside China	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)

  Note

  For a primary cluster deployed in a region in the Chinese mainland, you cannot deploy secondary clusters in China (Hong Kong) or regions outside China.

Pricing

You are not charged for the traffic that is generated during cross-region data transmission within a GDN. You are charged only for the use of PolarDB clusters in the GDN. For more information about the pricing rules of PolarDB clusters, see Billable items overview.

Create a GDN

1. Log on to the PolarDB console. In the left-side navigation pane, click Global Database Network.

2. On the Global Database Network page, click Create GDN.

   

3. In the Create GDN dialog box, configure the following parameters.

   Parameter	Description
   Name	The name of the GDN that you want to create. We recommend that you specify a descriptive name that makes it easy to identify. GDN names do not have to be unique.
   Primary Region	The region where the primary cluster is deployed. Note Select the region where the primary cluster is deployed.
   Primary Cluster	Select an existing cluster as the primary cluster of the GDN.

4. After you create a GDN, you can add secondary clusters. For more information, see Manage a secondary cluster.

Release a GDN

Log on to the PolarDB console. In the left-side navigation pane, click Global Database Network.

1. Find the GDN that you want to release and click Delete in the Actions column.

   Important

   • A GDN can be released if it contains only the primary cluster.

   • A GDN cannot be restored after it is released. Proceed with caution.

   • Applications that are connected to the endpoints of a GDN cannot access databases after the GDN is released. Modify the application code to change the connection string of the GDN at the earliest opportunity.

FAQ

References

• Manage a secondary cluster

• Connect to a GDN

• Create a global domain name

Related API operations