> > No, when we implemented high-availability MySQL servers we used MySQL's > inbuilt replication - this has been running here for years now and we have > had constant DB availability during that time, even though individual > machines have failed now and again. We're using 2 masters & 4 slaves with > the logic for sql reads going to the slaves and sql writes going to the > master handled in the application layer. We also have automatic master > failover (although I believe MySQL plan to build this into their product at > some point in the near future). >
At the moment we are studying the implementation of a MySQL-Apache high High Availability system. Would you be so kind to explain a bit more detailedly the soft/hard aspects of yours application?. I believe that at the moment this is a hot question. Probably there are many more people interested in yours experience. Greetings. A.J.Millan ZATOR Systems. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
