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

Wow what a lot has changed since the last MySQL conference I blogged about in 2007

MySQL has been acquired twice, once as MySQL by Sun and the second time around bundled with Sun when Oracle bought Sun. The conference is no longer organized by O’Reilly but by Percona. And the MySQL database itself has changed – We were talking about new features in MySQL 5.1, which wasn’t released yet, along with Falcon (where did it go?). 5.1 has long since been released as has 5.5 and we’re now talking about 5.6 instead of 6.0. There was no “Cloud” on the horizon, nor was there MariaDB, XtraDB, Drizzle, Schooner or any of the other offshoots of MySQL, all of which are creating a new buzz around the product.

Yet one thing remains constant – the vibrant community around

What makes you think jdbc autoreconnect is needed?
Application is idle for long periods at a time?
Wait_timeout too short?
Network failure or glitches?

Some good suggestions form Mark Matthews - Bug #5020

Having encountered the problem again myself today, trying to make jdbc for mysql reconnect any terminated connections using autoreconnect=true I figured out a way to work it out from the pooling side.


Introduction to the problem:

On the mysql side wait_timeout is set to default 8hrs and any connections idle for longer than that were beomg terminated despite setting the connection string to: url=jdbc:mysql://localhost:3306/dbname?autoReconnect=true. The application was thence throwing an exception.

The solution was to introduce a ping

I guess that it’s time for the 3rd annual “Ravelry Runs On” roundup. The last two were in March 2008 and March 2009.

This year, our traffic increased by 50% to 5,000,000 page views and 15 million Rails requests per day. We made very few changes to our architecture in 2009 but we did add a new master database server after our working set of data outgrew our memory and IO capacity.

This summary is more detailed then the last two and I’ve broken it up into rough sections.

Physical Network

We own our own servers and colocate then in a datacenter here in Boston. The datacenter provides us with a cooled

This is going to be a really short post, but for someone it could save an hour of life.

So, you’ve nothing to do and you’ve decided to play around with IPv6 or maybe you’re happened to be an administrator of a web service that needs to support IPv6 connectivity and you need to make your nginx server work nicely with this protocol.

First thing you need to do is to enable IPv6 in nginx by recompiling it with --with-ipv6 configure option and reinstalling it. If you use some pre-built package, check if your nginx already has this key enabled by running nginx -V.

The results should have --with-ipv6 option in configure arguments:

Here is my experience trying to run OpenBSD with XenServer 5 Enterprise.

• XenServer console doesn’t function properly as it keeps overlaying text displayed previously or anything you have typed into the console. Makes it very difficult to read and see what you are doing. As well it appears numerpad with numlock on does not work either. The best work around is to SSH into OpenBSD.
• Receiving the following error messages at boot up, “clock: unknown CMOS layout” and “rl0: watchdog timeout”. Yes the NIC is being detected as a Realteak 8139. If I check /var/run/dmesg.boot out of the two error messages I only see the “clock: unknown CMOS layout”. So I would assume the watchdog timeout