Help Center/ Data Admin Service/ Best Practices/ Fixing Insufficient Storage on DAS
Updated on 2024-12-30 GMT+08:00

Fixing Insufficient Storage on DAS

DAS intelligent O&M gives insights into space overview, disk space distribution, intelligent table diagnosis, disk space change trend, and top database tables.

This section describes how to fix insufficient storage of an RDS for MySQL instance.

Prerequisites

You have created an RDS for MySQL instance.

Procedure

  1. Go to the capacity analysis page.

    1. Log in to the DAS console.
    2. Click in the upper left corner and select a region and project.
    3. Click in the upper left corner. Choose Databases > Data Admin Service.
    4. In the navigation pane, choose Intelligent O&M > Instance List.

      Alternatively, on the Overview page, click Go to Intelligent O&M.

    5. In the upper right corner of the instance list, filter instances by engine, name, or IP address. Click Details to go to the Dashboard tab page.
      Figure 1 Intelligent O&M
    6. Click the Storage Analysis tab.

  2. Analyze the overall disk space.

    1. In the Used Storage area, view disk space distribution and usage.
      Figure 2 Disk space distribution
    2. Analyze which module is taking up your disk space and check the used space changes of that module.
      Figure 3 Used disk space
    3. After locating the anomaly on a day, check operations on the instance on that day and determine whether to release the space.

  3. Analyze data usage on the disk.

    1. The top databases and tables help customers locate abnormal increase in data size.
    2. Check the top databases or tables to find an unexpected data size.
      Figure 4 Top databases
    3. The space usage is abnormal.
      1. Delete invalid data from database tables.
      2. If invalid data cannot be identified, click View Chart to view the space usage changes and locate the time when the exception occurred.
        Figure 5 Data trend
      3. Obtain audit logs and SQL Explorer information of the instance at the time when the exception occurred. Delete the data which grew sharply due to abnormal changes.
    4. To clear up space, you can optimize tables with a high fragmentation rate during off-peak hours.

  4. Scale up the storage.

    1. Check the Overview area. If the remaining usage is less than 10% or the available space is less than 10 GB, you are advised to click Scale.
      Figure 6 Overview
    2. You can also toggle on Autoscaling. The instance storage will be automatically scaled up under certain conditions to ensure availability.
      Figure 7 Autoscaling

  5. Configure an anomaly detection alarm.

    After configuring a threshold, you can identify unexpected space usage increase on the Tablespaces page. When a sudden increase in data size exceeds the threshold (10 GB by default), an alarm is reported.
    Figure 8 Tablespaces