Deleting a Read Replica

Scenarios

You can delete read replicas billed on a pay-per-use or serverless basis on the Basic Information page.

Constraints

• Deleted read replicas cannot be recovered. Exercise caution when performing this operation.
• You can only delete a read replica when the instance has two or more read replicas. At least one read replica must be retained in the instance.
• If another operation is being performed on the instance, its read replicas cannot be manually deleted.
• For multi-AZ deployment, make sure that the primary node and remaining read replicas are located in different AZs after a read replica is deleted.

  If a primary node and a read replica are deployed in AZ1 and the other read replica is deployed in AZ2, the read replica in AZ2 cannot be deleted.

• Before deleting the last serverless read replica, ensure that the function for adjusting the number of serverless read replicas has been disabled.

Billing

Deleted pay-per-use or serverless read replicas are no longer billed.

Procedure

1. Log in to the TaurusDB console.
2. Click in the upper left corner and select a region and project.
3. On the Instances page, click the instance name to go to the Basic Information page.
4. In the Node List area, locate the read replica to be deleted and choose More > Delete in the Operation column.
5. In the displayed dialog box, click Yes. Refresh the Instances page later to confirm that the deletion has completed.
6. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

   Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

APIs

• Creating a Read Replica
• Deleting or Unsubscribing from a Read Replica