Jonathan, On Thu, Jan 08, 2004 at 12:54:06PM +0000, Jonathan Tullett wrote: > I am currently syncronizing two MySQL servers (version 3.23.49) on a > very high traffic website. > > There are, at peak times upwards of 600 updates a second (and many many > more selects) > > During these times the slave database will fall out of sync, sometimes > by several thousand seconds (im aware that this calculation is the 'time > now - timestamp of last update from the master) >
What is the status of the slave thread in show processlist? If it is 'Locked' then the slave thread may be starving because of too many (long) selects on the slave. > My question is: Is there any way I can ensure that the databases have > exactly the same data (ie, are in perfect sync), even if the overhead of > this check means that the servers themselves operate slightly slower? > If your my.cnf contains low-priority-updates and your slaves are serving selects continuously, then the updates won't come through. This setting is mentioned in the manual. If you remove low-priority-updates, the updates will be processed sooner but you'll get in trouble if you have long running selects. These will delay all following selects on the slave when an update is waiting for the long query to end. Fred. -- Fred van Engen XB Networks B.V. email: [EMAIL PROTECTED] Televisieweg 2 tel: +31 36 5462400 1322 AC Almere fax: +31 36 5462424 The Netherlands -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
