Major faults caused by inconsistent Master/Slave Data! Please note!

Fault description: master-slave architecture. After the master node is down, it switches to the slave node. As a result, the data consistency is not verified before the master node is down, the database cannot be verified. As a result, a large number of users cannot log on, resulting in complaints.

I wrote a PPT to check whether the Master/Slave Data is consistent.

Normal master-slave synchronization does not mean master-slave data consistency. Why? Here is an example:
The master database has a user and the password is 123456. The slave database does not have this user. If user a does not update the password, you can use show slave status \ G from the database and find that there is no error message because this record is not triggered. Believe it or not, you can try it.

So the following tool exists: note! This tool locks the table. The larger the table, the longer the lock time)

650) this. width = 650; "src =" http://img1.51cto.com/attachment/201308/180425568.jpg "style =" float: none; "title =" 1.jpg"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/220413HJ-1.jpg "style =" float: none; "title =" 2.jpg"/>

Note: The Master-slave architecture must ensure data consistency to avoid serious faults on my side today!

This article is from the "hechun's technical column" blog, please be sure to keep this source http://hcymysql.blog.51cto.com/5223301/1266203