All Products
Search
Document Center

PolarDB:Release a cluster

Last Updated:Oct 12, 2026

You can manually release pay-as-you-go PolarDB clusters based on your business requirements.

Usage notes

  • You cannot manually release subscription (prepaid) clusters.

    Note
    • For subscription (prepaid) clusters, you can manually Unsubscribe the cluster from the Clusters page. For more information about unsubscription rules, see Unsubscription rules.

    • Before unsubscribing from a subscription (prepaid) cluster, if you want to retain backups, go to Settings and Management > Backup and Restoration > Backup Policy Settings > General and configure the When Cluster Is Deleted option in advance. You can select Retain All Backups, Retain Last Backup, or Delete Immediately. After you unsubscribe from or release the cluster, you can view the retained backup sets in the cluster recycle bin. You can also delete the backups of a released cluster at any time to save costs.

  • Clusters that can be manually released:

    • Pay-as-you-go (postpaid) clusters whose Status is Running.

      Note

      If the Status of your pay-as-you-go (postpaid) cluster is Locking, your Alibaba Cloud account has overdue payments. You can top up your account while the cluster is locked. After the payment is completed, the cluster is unlocked and resumes normal operation. You can then manually release the cluster. For more information, see Expiration and overdue payments.

    • Serverless clusters whose Status is Stopped.

  • This operation releases the entire cluster, including all nodes in the cluster. To release an individual read-only node, see Add or remove nodes.

Procedure

  1. Log in to the PolarDB console,In the navigation pane on the left, click Clusters. Select the Region where the cluster is deployed, and then find the target cluster。

  2. In the Actions column on the right side, choose More > Release.

  3. In the Release Cluster dialog box that appears, select a backup retention policy and click OK.

    Backup retained

    Description

    Automatically back up and retain all backup sets for the cluster long-term

    When the cluster is released, all existing backup sets of the current PolarDB cluster are retained.

    Automatically back up and retain the last backup set long-term

    When the cluster is released, a full backup is performed, and only this backup set is retained.

    Delete all backup sets for the cluster immediately upon release

    After the cluster is released, all backup sets and logs of the current PolarDB cluster are immediately deleted.

    Warning

    Selecting this policy causes the current PolarDB cluster to become unrecoverable after deletion.

    Note
    • If you select the Automatically back up and retain all backup sets for the cluster long-term or Automatically back up and retain the last backup set long-term policy, when the PolarDB cluster is released, the system proactively performs a full backup to preserve all data before deletion.

    • After the cluster is released, if you selected the Automatically back up and retain all backup sets for the cluster long-term or Automatically back up and retain the last backup set long-term policy, the following rules apply:

      • For clusters with PSL4/PSL5 storage type, level-1 backups are automatically converted to level-2 backups and retained in the cluster recycle bin. A small fee is incurred.

      • For clusters with ESSD cloud disk storage type, data backups are retained in the cluster recycle bin. A small fee is incurred.

      You can delete the backups of a released cluster at any time to save costs.

FAQ

Can I pause or stop aPolarDBcluster?

  • If your PolarDB cluster has a fixed specification (the Billing type is Subscription or Pay-as-you-go), you cannot pause or stop the cluster.

  • If your PolarDB cluster is a Serverless cluster, you can enable the auto-pause and resume feature for the Serverless cluster. After this feature is enabled, the cluster automatically enters the paused state if no business connections exist within the Detection Period for No-activity Suspension. While the cluster is paused, you are still charged for storage on a pay-as-you-go basis. If any business connection is established, the cluster immediately resumes automatically.

Why am I still charged for backups after my cluster has been released?

If you chose to retain backup sets when releasing the cluster, backup storage fees are incurred accordingly. You can delete these backup sets from the cluster recycle bin to save backup costs. For more information, see Delete a released cluster.

Why can I not release my cluster?

Before releasing a cluster, check the following two items:

  1. Check whether Cluster Lock is enabled for the cluster. Check the Cluster Lock status on the cluster details page, or call DescribeDBClusterAttribute to check the DeletionLock field. If DeletionLock is set to 1, disable the protection lock first: on the cluster details page, disable Cluster Lock, or call the ModifyDBClusterDeletion API and set Protection to false. Then try releasing the cluster again. For more information, see Deletion protection lock.

    Note

    When the deletion protection lock is enabled, the release operation returns the OperationDenied.DBClusterDeletionLock error (error message: The operation is not permitted due to the deletion lock of cluster).

Troubleshoot charges when no clusters exist

If you have released all PolarDB clusters but are still being charged, follow these steps to troubleshoot:

  1. Check the cluster list in all regions: On the Clusters page in the PolarDB console, switch to each region one by one to check the cluster list and confirm whether any clusters exist that you may have overlooked. The region selector displays the number of clusters in each region.

  2. Check the cluster recycle bin: Go to the cluster recycle bin page in the PolarDB console to check whether any backup sets from released clusters exist. Retained backup sets incur a small fee. You can delete the backups of released clusters to save costs.

  3. Check cross-region backups: If the cluster had cross-region backups (level-2 backups) enabled before it was released, cross-region storage fees are incurred. Because the cluster has been released, you cannot view the backup policy from the cluster details page. You can go to the cluster recycle bin to check whether any backup sets from released clusters exist.

  4. Check billing details: In the Billing Management console, go to the Bills page, filter by PolarDB in the product name field, and review the specific charge items and amounts.

Related topics

Related operations

API

Description

DescribeDBClusters

Queries the list of PolarDB clusters.

DeleteDBCluster

Releases a pay-as-you-go (postpaid) PolarDB cluster.