In Soundbreak we play live audio and video 24 hours a day without interruption, so we can't make a very convincing test of MySQL's new copy feature. By testing we found that this feature can be used to keep data synchronized with the backup database server, so that when the primary server fails for some reason, it can use the backup machine to process all queries. For such requirements, it is not difficult to configure two servers. I'll discuss the entire process in detail, and discuss how to use PHP to redirect queries when the primary server fails.
The MySQL internal replication feature is built between two or more servers and is implemented by setting the master-slave relationship between them. One serves as the primary server, and the other as the slave server. I'll discuss in detail how to configure two servers, one set as the primary and the other from the server. and describe the process of switching between them. I was in MySQL's 3.23.23 version of the configuration setup process, and also in this version of the test. MySQL developers recommend that you use the latest version, and that the master-slave server uses the same version. MySQL version 3.23 is still beta, and this version may not be backwards compatible. So for this reason, in the actual website, I haven't used this version yet. One benefit of having fault tolerance is the ability to upgrade servers without interrupting any queries.
http://www.bkjia.com/PHPjc/532380.html www.bkjia.com true http://www.bkjia.com/PHPjc/532380.html techarticle in Soundbreak we play live audio and video 24 hours a day without interruption, so we can't make a very convincing test of MySQL's new copy feature. By testing US ...
