Help Center/
TaurusDB/
User Guide/
Multi-primary Instances (OBT)/
Deleting a Read/Write Node of a Multi-primary Instance
Updated on 2024-12-30 GMT+08:00
Deleting a Read/Write Node of a Multi-primary Instance
Scenarios
You can delete a read/write node of a multi-primary instance on the Basic Information page to release resources as required.
Constraints
- A deleted read/write node cannot be recovered. Exercise caution when performing this operation.
- You can only delete a read/write node when the DB instance has two or more read/write nodes. At least one read/write node must be retained in the instance.
- If another operation is being performed on a DB instance, the read/write nodes of the instance cannot be manually deleted.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Click in the upper left corner of the page, choose .
- On the Instances page, click the multi-primary instance name to go to the Basic Information page.
- In the Node List area in the lower part of the page, locate a read/write node and click Delete in the Operation column.
- If you have enabled operation protection, click Start Verification in the displayed dialog box. On the displayed page, click Send Code, enter the obtained verification code, and click Verify to close the page.
For details about how to enable operation protection, see Identity and Access Management User Guide.
- In the displayed dialog box, click Yes.
Parent topic: Multi-primary Instances (OBT)
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot