The causes and Solutions of relay-bin.xxxxxx after MySQL was switched from Library to main Library

This article mainly introduces "MySQL from the library to the main library after the causes and solutions", in daily operation, I believe many people in MySQL from the library to the main library after the causes and solutions of relay-bin. xxxx problems have doubts, small series consulted all kinds of information, sorted out simple and easy to use operation methods, hope to answer "MySQL from the library to the main library after the causes and solutions" doubts help! Next, please follow the small series to learn together!

There is a database. It was a slave database before, but later switched to the master database. The configuration of the master database in my.cnf has been commented out. The show slave status result is also empty. However, it has been found that a relay-bin. xxxx will be generated after using mysqldump backup (with--flush-logs) every day. Relay-bin.* has been deleted. After that, it will continue to occur. What happened? Google it and finally find out why.

http://bugs.mysql.com/bug.php? id=6178

After switching from the master library, you need to execute RESET SLAVE command, otherwise the master library configuration will still be cached in master.info file. After executing RESET SLAVE, master.info and relay-log.info will be deleted.

At this point, the study of "the reason and solution of relay-bin. xxxx after MySQL is switched from the library to the main library" is over, hoping to solve everyone's doubts. Theory and practice can better match to help everyone learn, go and try it! If you want to continue learning more relevant knowledge, please continue to pay attention to the website, Xiaobian will continue to strive to bring more practical articles for everyone!