mysql master master replication

MySQL5.6 master-slave replication (mysql Data Synchronization configuration), mysql5.6mysql Planning Master 192.168.56.2 Slave 192.168.56.5 1. On the master database, set a REPLICATION account rep1 and grant the

Mysql Master-slave replication principleWith the continuous development of the website business, the increasing number of users, the volume of data continues to grow, the number of database access is correspondingly increased, to a certain time, the first bottleneck of the site is in the database layer (here does not add the cache), this time the database needs t

MySQL supports one-way, asynchronous replication, in which one server acts as the primary server and one or more other servers act as the server. The master server writes the update to the binary log file and maintains an index of the log file to track the log loop. When a server connects to the primary server, it notifies the primary server of the location of th

MySQL master-slave replication1, basic master-Slave server configuration(1) Primary server configuration[Client]Port = 3306Socket =/tmp/mysql.sock[Mysqld]user = MySQLInnodb_buffer_pool_size = 128MLog_bin = Master-log ===========Max_binlog_size = 64MBinlog_format = Mixed ========Basedir =/usr/local/mysqlDataDir =/databa

experiences here: 1) The replication process of MySQL is an asynchronous synchronization process, not completely master-slave synchronization, so there is a delay in the synchronization process. If the read/write splitting service is enabled, we recommend that you monitor the delay; 2) the master and slave machines of

executing the following command on slave:Change MASTER to Master_delay = N; The Master_delay option is added directly #读者可在配置延迟从库Change master.This statement sets the slave database to delay n seconds and then replicates the data with the primary database by logging on to the Slave database server (this is 52) and then executing the following command.mysql> stop Slave;Query OK, 0 rows affected (0.45 sec)mysql