Shulou(Shulou.com)05/31 Report--

This article mainly explains the "introduction to the principle of mysql replication". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "introduction to the principle of mysql replication".

The master thread in the figure is every 1s refresh redo from redo buffer to disk.

Dump thread pushes binlog to remote slave, and each slave corresponds to a dump thread

The unit for receiving I / O threads and playing back SQL threads is event (write_row, etc.). Before 5.6, the SQL thread had only one thread, while the execution on the main library was multithreaded with large latency.

Multithreading is supported from 5.6. the previous SQL Thread is used as a coordinating thread, and the real thread for playback is Work Thread, but there is a problem in 5.6. Work Thread corresponds to the library. A library corresponds to a Work Thread,5.7 and starts to prepare the database consistent with the main database.

There are also two important files, master-info.log and relay-info.log,master-info.log, which represent the location of the pos received by the IO thread (the location of the event), and the relay-info.log represents the pos location to which it is played back.

Thank you for your reading, the above is the content of "introduction to the principle of mysql replication". After the study of this article, I believe you have a deeper understanding of the introduction of the principle of mysql replication, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.