Recently a database synchronization tangled for a long time, things are:
Master-slave database synchronization status is normal, no abnormal error log. However, where the data in a table can not always synchronized. (Data in the table has been no change). As the main library online business can not be stopped, the first small series think the problem may appear in the rights issue and look through all kinds of information, and authorities found no relationship; secondly, to try to re-create an instance of the corresponding synchronous main library, but full of ideal , have no doubt been the backbone of reality severely punctured. Bitter experience, decided to go even use database software, to modify the main library in the table, see if you can synchronize. Blindfolded, and even modify the data can be synchronized in the past, but the program still can not write to synchronize the past. Judgment is procedural issues can be no live ammunition before, how convincing. In the end, only the use of Terminator weapons, mysqllogbin to check the update data. Sure, there is update the database table name in uppercase. Check the main library, there is this argument lower_case_table_names, case-insensitive database table names;