This article explains the root cause and resolution for Amazon Aurora MySQL error 63955, which occurs when a cluster exhausts its internal virtual index IDs. It outlines why long-lived clusters with heavy DDL activity encounter this limit and provides a technical guide for performing a logical dump and restore to resolve the issue. The post also emphasizes configuring proper monitoring to receive early warnings for the overflow condition.
Key points
Error 63955 is caused by exhausting the 32-bit internal virtual index ID limit in Aurora MySQL.
This limitation is specific to Aurora MySQL and does not exist in upstream MySQL versions.
The only permanent resolution for an exhausted ID pool is a logical dump and restore into a fresh cluster.
Changing generated columns from VIRTUAL to STORED serves as a temporary workaround for individual indexes but does not fix the underlying ID exhaustion.
Use Aurora MySQL 3.10.0 or later to enable logging of the VIRTUAL_INDEX_ID_OVERFLOW_WARNING alert.