4 ms·
Yuck. Honestly, restarting a database to fix a major outage sounds like "we have no idea what we're doing"
by raffraffraff 5y ago
Yuck. Honestly, restarting a database to fix a major outage sounds like "we have no idea what we're doing"
- bpicolo 5y agoSporadic database performance issues can certainly make you feel that way. They are definitely not trivially debugged at scale
- vimda 5y agoWould you rather it stay down while they spend a day debugging it?
- paulryanrogers 5y agoIf that means it won't be down every morning in my time zone then yes.
- seanw444 5y agoAs long as it's announced in advance so that users/customers can plan ahead, I don't see why not.
- karmakaze 5y agoThey could use multiple writer hosts and rollover the restarts. MySQL has had GTIDs since 5.6 and replication groups rather than writer-replicas since some 5.7.x version.
- blueplanet200 5y agoIt sounds like "they don't know why it's going down." I've worked with plenty super competent people that have taken time to root cause incidents. Guide to incidents: Step 1: Stop the bleeding Step 2: Prevent it in the future Doing Step 1 doesn't make you incompetent.
- raffraffraff 5y agoI'm not a DBA, and maybe you're not a DBA either, so this question goes to DBAs who may be reading: aren't you always better off killing the bad queries instead of rebooting the whole box, if that's an option? (ie: aside from times when the entire host is screwed, load per core is >50, metrics aren't getting out, you can't ssh in etc)