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.
답변함 4년 전
관련 콘텐츠
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 일 년 전