From: James [mailto:[EMAIL PROTECTED] > Mike & Andrew, > Excellent ideas... > > The reason I am considering checking the log location, is > because normal lusers will be using this software, so it > won't be too good for them to see errors about the slave > being out of synch. (Some 20 people including my self are > using this software.) This is something that the software > will have to use some logic to figure out which slave is > the best. I will have a list of read slaves that I will > randomly call each program start, or upon error. Mike > did bring up a good point, false positives. > Has anyone done what I am talking about (checking bin log > position)? Also will this method actually remove load from > the servers? Thanks for your input so far.
A model of a write master and several read slaves is almost guaranteed to reduce load caused by db bottlenecking. We've seen it here in our setup. As for false positives: if possible, try whipping up a lengthy UPDATE query (or LOAD DATA INFILE) that you know will take a while. Start it on the master and, while it's cranking, manually check the binlog position on the master and slave(s). I'm not sure if such a load will cause a temporary discrepancy, but it's the first thing that comes to mind. -- Mike Johnson Web Developer Smarter Living, Inc. phone (617) 886-5539 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
