What error is shown by 'show slave status\G' on server C after you issue that query?
There's all sorts of things that could break replication... On Tue, Jan 20, 2009 at 7:21 AM, Krishna Chandra Prajapati <prajapat...@gmail.com> wrote: > Hi Baron, > > In production we have three servers. > > A----------------> B ---------------------C > > A is replicating to B. B is replicating to C > > A mysql-5.0.32 (Write) > B mysql-5.0.32 (Read) > C mysql-5.1.30 (Report Server) Complex and big queries scanning all > data. > > *ISSUE*: If any query like 'update set col1='val', col2=null where > userid=12345;' gets executed by webserver on A. (col2 is not null column) > Then query gets executed and data gets changed on A and B. But it gives > replication error on C. If i skip that error then data will be inconsistent. > Server C will have different data than A and C. > > How to solve this issue. > > Krishna Chandra Prajapati > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
