On this page

Show all

Help Center/ Document Database Service/ FAQs/ Database Storage/ Why Does a DDS DB Instance Become Read-only?

Why Does a DDS DB Instance Become Read-only?

Updated on 2022-12-12 GMT+08:00

View PDF

To ensure that a DB instance can still be used if the storage space is about to be used up, databases running on the instance are set to read-only, and data cannot be modified. If this happens, you can add more storage to restore the database to read/write status.

Detailed rules are as follows:

If the storage space you purchased exceeds 600 GB and the remaining storage space is 18 GB, the DB instance becomes Read-only.
If the storage space you purchased is less than 600 GB and the storage space usage reaches 97%, the DB instance becomes Read-only.
If the storage space you purchased exceeds 600 GB and the remaining available storage space is greater than 90 GB, the read-only state is automatically canceled.
If the storage space you purchased is less than or equal to 600 GB and the used storage space is less than 85% of the total storage space, the read-only state is automatically canceled.

You are advised to remove unnecessary resources or expand the storage space.

Parent topic: Database Storage

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel