Help Center> Relational Database Service> FAQs> Database Storage> What Should I Do If My Data Exceeds the Available Storage of an RDS for MySQL Instance?
Updated on 2023-04-20 GMT+08:00

What Should I Do If My Data Exceeds the Available Storage of an RDS for MySQL Instance?

Symptom

There is not enough storage available for an RDS instance and the instance becomes read-only, so applications cannot write any data to the instance.

You can check which data or files occupy too much storage in the Disk Space Distribution area on the Storage Analysis page. For details, see Storage Analysis.
Figure 1 Disk space distribution

Causes

  1. Increased workload data
  2. Too much data being stored
  3. Too many RDS for MySQL binlogs generated due to a large number of transactions and write operations
  4. Too many temporary files generated due to a large number of sorting queries executed by applications

Solution

  1. For insufficient storage caused by increased workload data, scale up storage space.

    If the original storage has reached the maximum, upgrade the specifications first.

    For instances using cloud disks, you can configure autoscaling so that RDS can autoscale your storage when the storage usage reaches the specified threshold.

  2. If too much data is stored, delete unnecessary historical data.
    1. If the instance becomes read-only, you need to contact customer service to cancel the read-only status first.
    2. Check the top 50 databases and tables with large physical files and identify the historical table data that can be deleted. For details, see Storage Analysis.
    3. To clear up space, you can optimize tables with a high fragmentation rate during off-peak hours.

      To delete data of an entire table, run DROP or TRUNCATE. To delete part of table data, run DELETE and OPTIMIZE TABLE.

  3. If binlog files occupy too much space, clear local binlogs.
  4. If temporary files generated by sorting queries occupy too much storage space, optimize your SQL statements.

    You can query slow query logs and top SQL statements, and analyze and optimize the problematic SQL statements.

  5. Subscribe to daily health reports to obtain SQL and performance analysis results, including slow SQL analysis, all SQL analysis, performance & storage analysis, and performance metric trend charts. You can receive a diagnosis report if there are any risks detected.

    For details, see Daily Reports.

Database Storage FAQs

more