8 months ago
Has anything changed in the last week or so regarding MySQL service restarts? I always used to just restart MySQL whenever its RAM usage inched up too high, and the service would become available in a few seconds. Now it seems to get stuck, and never becomes available. My workaround is to redeploy MySQL. It works, but it takes a bit longer to come back up.
13 Replies
Not sure if it's unique to my project, but here's my project ID just in case
8 months ago
Hello,
Can you please define never? how long have you waited in practice?
5-10 minutes, compared to 3-5 seconds a week ago. I couldn't afford to have my site down for any longer, so I panicked and redeployed. Interestingly, both dev and prod are now restarting quickly again.
8 months ago
Thank you for the report, if it happens again please let us know!
Seems to be intermittent. On project b855592c-9156-4020-9543-d41a4e939fde right now my dev environment MySQL database is spinning on the last step, after being restarted by your cron MySQL restarter service:
MySQL Data UI
A custom interface into your database
Deployment Online
This service has an active deployment
Required Variables
This service has all the necessary variables that this UI uses to connect to the database.
<<>>Database Connection
8 months ago
mysql is not running for that service
8 months ago
Yes, that's the problem. It looks like it was deployed and started running, but it's not. How do I get it running again? Does your cron MySQL restarter service do that for me?
8 months ago
you would want to re-deploy, but honestly you should not be continually restarting your database, you are at risk of data loss with a bunch of abrupt restarts
Generally I allow sleeping on the MySQL service, but my problem is that lately it's not coming out of sleep, and even restarting is not bringing it back up. In the last two years I've never had to re-deploy. Now I'm having to re-deploy often
8 months ago
Did you report that it doesn't wake on the central station?