The last Keynote was from none other than The Brian Aker, a keynote on the New MySQL Cloud Ecosystem. He was formerly the Director of Architecture for MySQL and also the creator of Drizzle. He is currently a fellow at HP, leading their cloud architecture group.
The next keynote is from Marten Mickos, now with Eucalyptus systems, previously CEO of MySQL AB. He’s talking about making LAMP a Cloud. No surprises there, Eucalyptus is the leading open-source cloud computing platforms for on-premise use.
Here it is finally – the MySQL conference 2012 starts with the Keynote Sessions. The first keynote speech is by Peter Zaitsev, founder of Percona and a very smart guy and also by Baron Schwartz (Percona), another very smart guy, the brains behind a number of toolkits for MySQL.
A very well attended Pedro’s dinner – I didn’t count, but we had 9 tables of 8-10 people or so – dare I say almost a 100 people? Lots of beer, margaritas and good conversations! Here are a few pictures from the event
If you’re at the conference, please come join us for the MySQL Community Dinner at Pedro’s and meet some of the people behind Pythian. We’re always hiring so if you’re interested, please attend the talks and tutorials being presented by Pythian folk, talk to us or check out the job openings
Pythian organizing an event that by now may be considered a tradition: The MySQL community dinner at Pedro’s! This dinner is open to all MySQL community members as many of you will be in town for the MySQL Conference that week. Here are the details..
This release is just a quick bug fix release of an older 1.1.1 version of the plug-in. It’s long overdue but I’ve managed to fix “” problem only couple weeks ago. I’ve distributed the new version to the folks who have reached out to me by email of via blog reporting the issue in the past few months and they all confirmed that the new version is working fine so I’m releasing it now.
A few days ago, we faced a Duplicate entry problem in the mysqld server on one of our customer’s slave after cold backup. We made some recommendations to the Customer (read them here) in which the option 3 was chosen as the slave was dedicated for backup’s and a quick solution applicable for their data set and timeline for resolution of the issue.
I had to refresh my knowledge on how InnoDB threads queue works the other day when debugging activity spikes on one of the customer’s production system and while I had general idea about InnoDB kernel and queue, thread concurrency and queue join delays I didn’t have a complete model of how InnoDB concurrency control works. So I started from manual…
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.