MySQL’s replication system has been a core feature often touted for scaling (sort of) and redundancy (sort of). I’ll outline several uses, misuses, and “yes, it will work but i don’t recommend it” implementations.
For this presentation, I’ll describe a current client’s extensive use of MySQL replication (they have more than 200 MySQL instances in 4 geographically disparate locations replicating to one another) touching on what works, why it works and where there are better options if this infrastructure was to be rebuilt from scratch. I’ll cover: multi-master replication, read only slaves, replication loops, reporting spurs, consistency checking, time delayed replication, latency and it’s affects on these architectures, monitoring, bottlenecks etc.
I’ll also touch on why they’re still running 5.0 and what the changes to replication in MySQL’s 5.5 release might mean for upcoming projects.
I’m a founding partner of Blue Gecko. I manage and am a senior administrator in the Open Databases / LAMP practice. We do remote administration and management of databases around the world.
I additionally run the Seattle meetups for LinuxChix, MySQL, and one focused on Opensource and general geeky socializing.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at email@example.com
For media partnerships, contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference Bulletin (login required).
View a complete list of O'Reilly MySQL Conference Contacts