Shulou(Shulou.com)06/01 Report--

Related article: https://blog.csdn.net/yabingshi_tech/article/details/50736735

Description:

In fact, binlog does not need to be changed as long as the database in the replication relationship is synchronized. That is, reset master does not need to be executed in a normal state. Instead, in cascading replication, if the intermediate server performs reset master, the binlog of the intermediate server will be reset. The consequence is that subsequent cascading replication databases from the intermediate server will need to reset the replication starting point. In this way, it is difficult to confirm whether the original POST location is correct.

When does it need to be implemented, or must it be implemented?

1, there is a downtime!

Downtime means data may be lost. Well, after the first choice to complete the BINLOG from the database, it is difficult to say that there is no data loss. At this point, both reset master and reset slave should be executed to start another log cycle.

2, the data was written unexpectedly from the library

After the slave library is accidentally written to the data, the slave library must be inconsistent with the master library. In fact, the slave library needs to be rebuilt at this time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.