-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6.x] MySQL Aurora failover - DetectsLostConnections #31539
Conversation
Here is full output of log file while command is running and failover is happening [2020-02-20 09:50:58] macbook.DEBUG: second: 58 [] [] |
Is there any updates on this issue?. We are facing on the same one. |
@Manikandan85 - This was merged and we have not had any issues with queue workers since. Though I'm not sure we've experienced a failover since. |
okay. Thank you @IndexZer0. I will replicate the failover and check whether it fixes it. |
Same situation described here: laravel/framework#31539
Same situation described here: laravel/framework#31539
We recently experienced a MySQL Aurora failover on production and noticed that our queue workers didn't restart.
When running the following code inside a Laravel command and then starting a failover inside RDS dashboard we see these exception messages:
brand_daily_summary
setdeposit_count
= 23 whereid
= 1)Maybe
protected function causedByLostConnection
is not the correct place to be handling the--read-only option
exception message though as it is quite general?Any thoughts on this?