Discussion Board

MySQL replication not running updates in binlog

+2
Votes
0
Comments
I have a number mysql servers running version 5.1.63 and whilst running some queries against the slave earlier this week, I noticed some data on the slave that should have been removed using an update statement on the master. My initial thoughts were: someone on the team was updating the slave, which I have since disproved that the column being updated had changed So, I investigated by running a mysql show status "table" query. This was run against a test database on each of the servers to see what the data length was, in a lot of cases it was showing me the data length differed between servers, but on an eyeball look at the data I could see the data was the same, so I couldn't use this method to see if there were any differences as it appears to be prone to error. Next I ran a simple (across all dbs) row count for each table to confirm the row count was the same - it was. I then started looking in the bin logs for replication. I could see the update statements that should have run clearly visible in the logs, but the update never ran. What I need to know is: is replication broken? I'm assuming it is if I create new slave servers, will I encounter the same issue? how do I find out the extent of the issue on my servers? Any help is appreciated.
posted in Technology by Maida Barrientos Mar 04,2015 03:48 am