Author: Andrew Moore

I’ve been pondering the next step in my training path; what do I want to learn or improve upon? You see, here at Pythian we’re encouraged to be the masters of our own progress. If you’re ever lucky enough to…

Just a silly article about a couple of instances recently where my colleague and I have both been duped by scheduled jobs. The feint and obvious lesson here is to be aware of your surroundings.

Andrew Moore and Ben Mildren return from Ottawa to Bristol to London all in the name of MySQL

Join Francisco Bordenave from Pythian’s MySQL team for a presentation on replication, old and new.

The Keynote talks included some words from Peter and Baron of Percona, Martin Mickos now of Eucalyptus Systems, and Brian Aker of HP. I was impressed by the new HP cloud product powered by OpenStack and now with an Aker-driven DaaS backed by a tuned Percona Server. It was interesting to watch the demo video on creating new instances as well as the snapshots of existing instances to create cloned instances. I would like to review this for myself and now will since the HP guys were offering to send beta access to the attendees.

The MySQL errorlog is an important point of reference when administering a MySQL Server. We can grasp much about the state of our MySQL instance by the informational and error messages written out to it by our MySQL daemon. I was asked to investigate some replication outage alerts a colleague had received overnight. One of the primary directions I took was the error log file. This is where I would expect find any evidence of replication being stopped or crashes etc. When I ran the command to tail the log I was shocked to see the log was totally empty.