Sometimes not possible to connect to database after downgrade
Last week we decided to downgrade db.r5.large to db.m5.large (which is basically a downgrade from 8GB RAM to 4GB RAM). Eversince I am experiencing sometimes a notification our website is not possible to connect to the database. However when I look at CloudWatch, all should be fine. I have attached a screenshot of the db's cloudwatch. Not sure if I am missing something here or if maybe the downgrade caused a bug? Yesterday evening I did decide to give an upgrade to MySQL 5.7.42 and change from gp2 to gp3. It does seem this helped it a bit but it is still happening.
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Probably just a typo, but a downgrade from db.r5.large to db.m5.large is going from 16GB to 8GB. But regardless, the FreeableMemory looks alright.
Did everything else remain the same with the instance, in particular the new db.m5.large is definitely in the same DB subnet group as the old db.r5.large ?
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for your answer. Actually I do think its already fixed after going from gp2 to gp3 and updating mysql to 5.7.42. The database connection error that was showing might have been from cache as I did not hear it happen anymore.