2回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
It seems likely that you have a data inconsistency in the innodb tables space. This gets propagated into a new read replica or a restore from backups. I'd recommend you use mysqldump to extract data from your instance and reload it back into a new instance to fix the metadata inconsistency.
-Phil
0
There was a corrupted index on a table. reading or writing a specific row in the table would cause the server to reboot. I created a new database from scratch from the code, and then transferred all records semi-manually using MANY mysqldump statements over several weeks - the db is 11TB.
No problems since.
回答済み 5年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 3年前
- AWS公式更新しました 1年前