Aurora v2.10.2 - MySQL Server Has Gone Away
Since upgrading our Aurora cluster to v2.10.2 a couple of weeks ago we have experienced intermittent "MySQL server has gone away" errors on the Writer instance. So far the readers are not affected. These occur at seemingly random times to queries on various tables. The errors did not occur prior to upgrade.
All RDS logs are empty, except for the external/mysql-external.log file. This file appears to show the server being restarted, but it does not include any timestamps or other information that could be used to tie it back to the "MySQL server has gone away errors"
This file has now grown to over 80mb in size.
We are already on the latest Aurora engine version for v2. Any assistance would be appreciated.
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I'd recommend opening up a support case so the RDS team can look into this issue. Support has access to tooling to review the health of your RDS instances.
There are several causes for the server gone away error described here.
You can view RDS Events, including restarts, by following this guide.
Were you able to get this solved ? We are experiencing an identical issue.
I am also facing the same issue. I have tried all the possible changes like. wait_timeout, interactive_timeout, max_allowed_packet but no luck. Is there any solution you found
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa