[7.x] Add PDOException's try again as a lost connection message - #32544
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since switching to AWS Fargate, we started to encounter the error below time to time when connecting to the databases. It just suddenly comes out from nowhere and disappears in a second or so.
Of course we are investigating what's going on under there, but at the same time, I feel that Laravel should retry to create connection since it's saying "try again".
I added the whole message including
SQLSTATE[HY000] [2002]since there was a discussion taken place before, claiming there was a side effect when the message was too general.( added here #25289, but reverted here #27053 )