Replication began to work not always, not right away
Posted by:
Dan Mor
Date: March 31, 2012 02:47PM
Hello!
I have strange bug, or I just do not understand all must be setted.
I have MASTER version '5.5.21-log'
and SLAVE version '5.5.21'
Replication all is done such as in all tutorials. All seems to be working - SLAVE always update its binlog position, observing the master, no error happens, after I set "slave-skip-errors=1062,1146"
but when I do some UPDATE-queries on MASTER, SLAVE renew the log-position, nut DO NOT make changes to database field values!!
And when some time passed (some hours), changes began appear, when new changes are done on master - so new logs began to process correctly. BUT those first changes that I make after replication was started - they still not appear in SLAVE database, so databases of SLAVE & MASTER come to be not synchronized!
I was tested it both in MYISAM and InnoDB tables. Effect is the same.
Why that start lag appears, can anybody explain me please?