A global database network (GDN) consists of Apsara PolarDB clusters distributed in different global regions. Data is synchronized across all clusters in the network. When your business is deployed in multiple regions, you can use a GDN to gain instant and reliable access to databases. This topic describes how to remove a secondary cluster and release a GDN.

Remove a secondary cluster

  1. Log on to the Apsara PolarDB console.
  2. In the left-side navigation pane, click Global Database Network.
  3. Find the target GDN and click GDN ID/Name.
    ID
  4. In the Clusters section, find the target Secondary Cluster, click Detach in the Actions column.
    Note
    • The whole detachment process requires about 5 minutes.
    • During detachment, all the connections to endpoints of the GDN and the secondary clusters are not interrupted. In this scenario, you can access databases as expected.
    • Only secondary clusters can be detached from a GDN. The primary cluster cannot be detached from a GDN.
    • After a secondary cluster is detached from the current GDN, the primary cluster stops synchronizing data to the secondary cluster. At the same time, the secondary cluster is set to read/write.
    • After a secondary cluster is detached, the cluster cannot be added to the GDN again as a secondary cluster. Proceed with caution.
    Detach a cluster
  5. In the Detach Cluster from GDN dialog box that appears, click OK.

Release a GDN

  1. Log on to the Apsara PolarDB console.
  2. In the left-side navigation pane, click Global Database Network.
  3. Find the target GDN and click Delete in the Actions column.
    Notice
    • You can release a GDN when only one primary cluster exists in the GDN.
    • A GDN cannot be restored after it is released. Proceed with caution.
    • Applications that are connected to the GDN endpoints can no longer access databases. You need to modify the GDN endpoints in time.
  4. In the Delete GDN dialog box that appears, click OK.