1. MySQL master-master replication + LVS + Keepalived implements MySQL high availability
Introduction:: MySQL master-master replication + LVS + Keepalived implementation MySQL high availability: MySQL replication can ensure data redundancy and can separate reading and writing to share system pressure. If it is master-master replication, it can also avoid single points of failure of the master node. However, MySQL master-master replication has some problems that cannot meet our actual needs: it does not provide a unified access entrance to achieve load balancing. If the master fails, you need to manually switch to another master instead of automatically switching. The following article will introduce how to achieve high availability of MySQL through LVSKeepalived and solve the above problems at the same time. K
2. Mysql master-master synchronization primary key conflict handling in production environment
Introduction: After receiving the SMS alarm, two Both databases reported that slave synchronization failed. Let’s first explain the environment and architecture: lvs+keepalived+amoeba+mysql, master-master replication, single-server write, master 1:192.168.0.223 (write) master 2:192.168
3. MySQL dual master high availability architecture MMM practice
##Introduction: Introduction to MMM: MMM is Master-MasterReplicationManagerforMySQL (mysql master-master replication manager). It is a scalable script suite for monitoring, failover and management of mysql master-master replication configuration (in
4. MySQL-MMM switching demonstration
##Introduction: MMM (Multi-MasterReplicationManagerforMySQL) is based on a dual Master structure, followed by N Slaves. The installation is very simple. The official website provides very detailed installation documents: http://mysql-mmm.org/mmm2:guide
5.
MySQL master-slave, master-master replication and high availability
Introduction: Pass the ddl and dml operations of the master database in the master server through the binary log Pass it to the slaves server, and then re-execute these log files on the master server, so that6.
MySQL two-way replication (main master mode)
Introduction: MySQL two-way replication (primary-primary mode) Environment: A: 192.168.1.1 No data B: 192.168.1.2 No data Add under the [mysqld] field of A: auto-7.
MySQL master-active and mutual-standby architecture configuration under CentOS 6.3
Introduction: MySQL master-active and mutual-standby structure is based on mysql Based on incremental logs, it is different from the master-slave replication structure. In the master-master replication structure, the data inventory on any one of the two servers occurs8.
Mariadb10 read-write separation based on Multi Master MySQL (MMM)
## Introduction:----Outline of this article Introduction to the resource configuration topology diagram implementation process ==================== 1. Introduction MMM is Master-MasterReplicationManagerforMySQL (mysql master-master replication manager) About mysql master-master replication
9.
MySQL master-slave, semi-synchronous, master-master replicationIntroduction: We know that the binary log of the MySQL database Records every sql statement that may explicitly or potentially cause changes to the database, so we can implement it based on the binary log
10.
MySQL5.5 master-master replication configuration method and Test resultsIntroduction: 1. Environment: CentOS5.5 x84, MySQL5.5.152. Two machines: master1:192.168.5.143master2:192.168.0.1493. Compile and install separately MySQL, and test the connection
The above is the detailed content of Let's talk about usage examples of master-master replication. For more information, please follow other related articles on the PHP Chinese website!