On Tuesday 03 August 2004 01:11 pm, Jon Drukman wrote: > We were having terrible problems with a master/slave setup. The master > does a huge amount of writes, and the slave simply started lagging > behind, despite both machines being identical hardware-wise. This made > the application basically unusable because eventually the slave was > hours behind the master, and had no chance of ever catching up. I > disabled InnoDB on the slave (skip-innodb in the my.cnf file) and now it > has caught up and is keeping up fine.
This is a horrible solution.. It clearly states in the docs that a heavily write screnerio is bad news for replication.. You have to realize the slave has to process everything the master does.. Replication is good for more of more read/ some write scenerio. You need a cluster.. Jeff -- ======================================================================= Jabber: tradergt@(smelser.org|jabber.org) Quote: You can lead a user to the manual, but you can't make him read. =======================================================================
pgpgW7SSzKws8.pgp
Description: PGP signature
