1114 aws resource_error ai_generated true

MySQL server has gone away: error 1114 (HY000) The table is full

ID: aws/rds-storage-full-read-only

Also available as: JSON · Markdown · 中文
90%Fix Rate
88%Confidence
1Evidence
2024-01-10First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
mysql-8.0.35 active
aurora-mysql-3.05.0 active
rds-2024 active

Root Cause

RDS instance storage volume is full, preventing write operations and causing MySQL to terminate connections abruptly.

generic

中文

RDS实例存储卷已满,阻止写入操作,导致MySQL突然终止连接。

Official Documentation

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html

Workarounds

  1. 90% success Increase the allocated storage for the RDS instance via AWS CLI: aws rds modify-db-instance --db-instance-identifier mydb --allocated-storage 200 --apply-immediately. Then wait for modification to complete.
    Increase the allocated storage for the RDS instance via AWS CLI: aws rds modify-db-instance --db-instance-identifier mydb --allocated-storage 200 --apply-immediately. Then wait for modification to complete.
  2. 85% success If using Aurora, enable storage autoscaling: aws rds modify-db-cluster --db-cluster-identifier mycluster --enable-http-endpoint --auto-minor-version-upgrade --storage-type aurora --allocated-storage 100 --max-allocated-storage 1000
    If using Aurora, enable storage autoscaling: aws rds modify-db-cluster --db-cluster-identifier mycluster --enable-http-endpoint --auto-minor-version-upgrade --storage-type aurora --allocated-storage 100 --max-allocated-storage 1000

中文步骤

  1. Increase the allocated storage for the RDS instance via AWS CLI: aws rds modify-db-instance --db-instance-identifier mydb --allocated-storage 200 --apply-immediately. Then wait for modification to complete.
  2. If using Aurora, enable storage autoscaling: aws rds modify-db-cluster --db-cluster-identifier mycluster --enable-http-endpoint --auto-minor-version-upgrade --storage-type aurora --allocated-storage 100 --max-allocated-storage 1000

Dead Ends

Common approaches that don't work:

  1. 95% fail

    重启不会释放存储空间,写入操作会立即再次失败。

  2. 70% fail

    删除索引只能释放少量空间,且可能影响查询性能,不足以解决存储满的问题。