Michael D. Posted December 13, 2016 Report Share Posted December 13, 2016 Hello, This morning we were alerted by a few users that MySQL on the server was performing much slower than usual. While attempting to resolve this matter the server eventually went unresponsive forcing us into a reboot. We did manage to get a graceful reboot fired off so that MySQL could shut down gracefully and not damage any databases or tables. The server is as of now back online. We anticipate the server to function a bit slower than usually for the first 5 to 15 minutes as system caches and buffers refill. Our forums, these - you're viewing now, are actually running on the P1 server . Being that this was a standard reboot and not a forced reboot we do not anticipate any lasting issues as a result of the restart. In the event that you do have any issues you believe are related to this reboot - do please open a support ticket so that we can investigate. Sorry for the trouble this has caused and we appreciate your patience and understanding in this matter. Quote Link to comment Share on other sites More sharing options...
Michael D. Posted December 14, 2016 Author Report Share Posted December 14, 2016 I just snagged this image from one of our monitoring platforms. This is actually the average CPU usage per CPU core. You can clearly see the instability leading up to the shutdown [the huge spike in the graph before the lines disappear] followed by the smoothness and stability of the graph after that point. Ideally the server will remain stable and smooth - but we are actively watching it over the next few days so we can address any issues before they become large. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.