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.

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.

2. If too much data is stored, delete unnecessary historical data.
   1. If the instance becomes read-only, you need to contact technical support to cancel the read-only status first.
   2. 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.