[11.X] Postgres Aurora failover - DetectsLostConnections #53404
Merged
Conversation
This file contains 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
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.
We recently experienced a Postgres Aurora failover on production and noticed that our queue workers didn't restart. We are using read and write endpoints for the database connection in
database.phpand when Aurora fails over, the writer connection becomes a reader, but Laravel is trying to perform writes on it.The exception message we are getting:
SQLSTATE[25006]: Read only sql transaction: 7By adding this exception to the list lost connection in
DetectsLostConnections.php, Laravel should reconnect to the right connection.