Re: Solving problems with mysql replica
There is no 100% solution. There are many 99.9...% solutions. My preference is dual-master-single writer. That is with two servers set up to be master and slave to each other (as you have), but with writes going to only one server. Furthermore the two servers are in two different physical locations (think flood, earthquake, tornado, etc).
If one server goes down, your monitoring will alert you, and you will failover to the other. The system will be down for minutes (or more), depending on your response time.
Depending on the application and the code, you can probably INSERT more than 100 rows per second, possibly more than 10,000/sec. If that is not enough, then we can discuss alternatives; but let's discuss INSERT speed, not HA.
Consider MHA or Continuent as ways to "automatically failover. Each has limitations.
Dual-master has various problems when you write to both machines at the same time.. Writing to only one machine eliminates most problems.
Furthermore, since every write has to be performed on every machine, writing to both Masters does not provide "write scaling".