There is no regrets in the world, and once you make a mistake, you regret it. As an operation and maintenance, especially when accidentally deleting data in the database, it is even more costly. For MySQL, there is a way to avoid this tragedy.
The so-called delay here is not a frequent network delay, but we deliberately slow down the pace of copying from the library, such as letting the library 30 minutes slower than the main library. In this way, if the data is found to be problematic within half an hour, it can be remedied.
MySQL 5.6 already supports delayed replication. It can set the delay time of the standby node. It makes sense to delay replication, such as preventing the master node from accidentally deleting data, checking the history status of the database, and so on.
Configuration is not difficult, after finishing the master and slave, add this sentence:
CHANGE MASTER TO MASTER_DELAY = N;
The N unit here is seconds, so the slave library will be delayed by N seconds from the main library. After doing this, you can see the value of SQL_Delay in show slave status.
SQL_Delay: xxx
Bluetooth Speakers,Bluetooth Speaker,Portable Speakers,Mini Speaker
Dongguan Guancheng Precision Plastic Manufacturing Co., Ltd. , https://www.dpowergo.com