Jay Jenssen talks about Yahoo!’s approach
Now, what makes our solution different? Not much. The layout is this: two master databases, one in each of our two colocations. These masters replicate from each other, but we would never have more than two masters in this replication loop for the same reason we don’t use token ring networks today: one master outage would break replication in a chain of size > 2. Our slaves replicate from one of the two masters, often half of the slaves in a given colocation replicate from one of the masters, and half from the other master.
But there is much more in the original article (e.g. allowing writes to a single master, dealing with failure, etc.). There are also three slide decks on infrastructure resiliency, high availability/business continuity planning, and application resiliency.
Infrastructure resiliency at Yahoo
High availability/Business continuity planning at Yahoo
Application resiliency at Yahoo
It doesn’t sound so exciting as what Google is doing, or Facebook, but it is probably something many could learn from.
Original title and link for this post: High Availability MySQL at Yahoo! (published on the NoSQL blog: myNoSQL)