Help Center/ Document Database Service/ FAQs/ Database Storage/ Why Does a DDS DB Instance Become Read-only?
Updated on 2022-12-07 GMT+08:00

Why Does a DDS DB Instance Become Read-only?

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.