Downtime again. Sigh.
We’re down again due to a MySQL error. Luckily this time I had the opportunity to witness this corruption process in action. What occurs is that MySQL’s CPU usage would spike up to 100% on all CPUs of the server. Soon after that a series of errors are outputed into the error log and MySQL automatically restarts.
The worst part of this is that the database may become irrecoverable. This has happened before in previous crashes. Every crash however seems different in terms of the errors that is outputed.
But from looks of things, the current back up we’re making seems to be getting through.
