2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Thank you for the note. May I ask - Why didn't you move to a Graviton2 instance by upgrading the primary or the reader instance? The downtime with this approach is just 60-120 seconds. We always suggest using native tools rather than AWS DMS for homogeneous migrations.
con risposta 2 anni fa
0
A key gap here is that the UI does not indicate that the instance types have been filtered based on the Aurora version. I would lose 10 inserts per second during any downtime. So the only option I could see was to use DMS. I spent about 6 hours battling DMS because the DMS info omitted to mention the requirement to restart the cluster after changing the parameter group to allow replication. I only found this detail by chance on a parameter group doc page.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
At the cluster level, there is no option to change the instance type. At the instance level, the only options are to move to another db.r5.* type. db.r6g is not offered. I am contemplating upgrading first from Aurora 1.22.2 (MySQL 5.6) to Aurora 2.10.2 (MySQL 5.7) - will there be an option to switch to Graviton2 after that?
A native tool is going to cost me far more time than 60-120 seconds.
Yes, that will work.