Running Multiple MySQL Instances On a Single Server

Ben Black (Garmin), Mark Filipi (Garmin International)
Average rating: ***..
(3.00, 3 ratings)

At Garmin we were getting too many mysql servers to maintain. We decided to try consolidating MySQL instances onto fewer physical servers. We didn’t want to use server virtualization due to the overhead and memory ballooning that come with VMWare. We had trouble finding much information about running and managing multiple MySQL instances together on a server.

We now have a standard repeatable build for all MySQL servers, including the OS and MySQL instances. We currenly have two people managing 80 MySQL instances. We are using Puppet to configure the servers. We are able to rapidly deploy new instances in as little as 15 minutes.

Each MySQL instance has its own IP, data directory, log directory, start/stop scripts, proxy, and is part of a load balanced pool for planned maintenance and failover. We are able to have multiple versions of MySQL, and rapidly switch between them for testing. We are able to upgrade a single instance without affecting the other instances on the same server. All production instances are paired with a slave for backups and redundancy. Some backups use mysqldump and some use LVM snapshots and scp. We use an F5 load balancer. Each F5 pool usually has four entries, the master proxy and database and the slave proxy and database. We route traffic through the master proxy first so we get query analyzer information. It will automatically failover to the master database if the proxy fails. The standard is manual failover to the slave, but we have a few systems that are able to failover and failback automatically. By utilizing the SAN with LVM, we can add disk space while the databases are still running.

There are also some tricks you can do with LVM and multiple instances, like running a slave and taking a writable snapshot then starting a MySQL instance against the snapshot so that developers can test applications against up to date data. The slave stays up to date and you just stop the second instance, remove the snapshot, take another snapshot, and start the slave periodically to instantly refresh.

Ben Black

Garmin

Ben has been a DBA at Garmin since 2001.

Mark Filipi

Garmin International

Mark is a DBA at Garmin.

  • Oracle
  • Monty Program
  • Calpont
  • Facebook
  • Gear6
  • Infobright, Inc
  • JasperSoft
  • Joyent
  • Kickfire
  • NorthScale, Inc.
  • Percona
  • Schooner Information Technology
  • Solid Quality Mentors (SolidQ)
  • Intel
  • Pentaho
  • Linux Pro Magazine

Sponsorship Opportunities

For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at yromaine@oreilly.com

Download the O'Reilly MySQL Conference & Expo Sponsor/ Exhibitor Prospectus

Media Partner Opportunities

Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com

Press and Media

For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com

O'Reilly MySQL Conference Newsletter

To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference newsletter (login required).

Contact Us

View a complete list of O'Reilly MySQL Conference contacts.