I. Tutorial purpose:
Mysql also supports semi-synchronous replication in master-slave replication. mysql replication is asynchronous because of poor synchronization performance. After the master database distributes events, you must wait until the slave database completes co
addition to the information contained in the Log, the returned information also includes the name of the Binary Log file on the Master end and its location in the Binary Log;
3.? Slave? After receiving information, the IO thread will write the received Log content to the end of the Relay Log file (mysql-relay-bin.xxxxxx) of the Slave end in sequence, and record the file name and location of the bin-log on the Master end to the master-info file, so th
large2. User write request will not be completed after master outage3. Node data may be inconsistent4, the default use of asynchronous replication mode5. Delay reasons for the delay:1,slave node too much, master will open a dump thread for each slave2, Concurrent write request operation, because MySQL supports concurrent requests, if multiple write requests arrive at the same time, these writes will be re
MySQL Master-Slave replication (Master-slave) practice, mysqlmaster-Slave
The master-slave replication function provided by the MySQL database can easily implement multiple automatic data backups and expand the database. Multiple data backups not only enhance data security, but also further improve database load perfor
Experiment MySQL with the plug-in provided by Google, complete the semi-synchronous replication model;The physical machine is still the Win7 system, the virtual machine is centos7;Master node: 192.168.255.2From node: 192.168.255.3Configure the primary from the replication model first:On the master node:]# vim/etc/my.cnf650) this.width=650; "src=" Http://s5.51cto.
= mysql-relay-bin
Relay_log_index = mysql-relay-bin.index
Read_only = 1
Skip_slave_start = 1
Log_slave_updates = 1
Note: If the user has the SUPER permission, read_only is invalid.
NOTE: With skip_slave_start, replication will not START on the server unless the start slave
according to pleaseThe request information reads the log information after the specified log location, and returns the Io_thread to Slave. Returns information in addition toThe information contained in the log, including the information returned to the Master side of the Bin-log file, andBin-log POS;3), Slave Io_thread received the message, the received log content is added to the Slave side of theRelay-log the end of the file and logs the filename and location of the Bin-log read to the Master
=192.168.10.34 #指定主服务器IP地址Master-user=slave #指定定在主服务器上可以进行同步的用户名MASTER-PASSWORD=YOURPASSWD #密码MySQL version is less than version 5.7 to configure the above three sentences. Version 5.7 only needs to be configured:server-id=2 #从服务器ID号, do not be the same as the primary ID, if you set multiple slave servers, each slave server must have a unique Server-id value that must be different from the primary server and the other from the server.Server-id values
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> change MASTER to Master_delay = 20; #这是延
fileMysql_install_db-datadir =/var/lib/mysql3307-user = mysqlC. start multiple instancesRun mysqld_multi-config-file =/etc/my. cnf. multi report to view the running status of multiple instances. The result is as follows:MySQL server from group: mysqld1 is runningMySQL server from group: mysqld2 not runningIt indicates that instance 1 is running and instance 2 is not running. you can use:Mysqld_multi-config-file =/etc/my. cnf. multi
directory:/home/mysql/mysql (use source installation, standalone directory)Server slave:192.168.14.132Mysql installation directory:/home/mysql/mysql2. Modify the configurationIn order not to affect the original configuration file:/etc/my.cnfCreate a new configuration file,Cp/etc/my.cnf/home/mysql/
master-port = 3306 master-connect-retry = 60 binlog-do-db = hrkip_zhhwd binlog-ignore-db = mysql binlog-ignore-db = information_schema binlog-ignore-db = phpmyadmin replicate-do-db = hrkip_zhhwd replicate-ignore-db = mysql,information_schema
5. Check whether the configuration is normal (l check the two servers separately ):
Start the slave service and run it on
process is slow, it is reasonable to use mysqldump to export the data on the master server, import the data to the slave server, and then start synchronization.
4. Preparation:Create a test table on the master serverMysql> create database data;Query OK, 1 row affected (0.03 sec)Mysql> select * from data.info;+ ----- + ------- + ----- +| Sid | name | age |+ ----- + ------- + ----- +| 1 | zhang | 23 || 2 | l
, and then the master operates the table, or causes the master to never synchronize, it is said that it can be configured as the main master mode, but I have not studied it yet. (2) The primary database server is down, and the business system needs to be manually switched to the slave database server. High availability is not possible (unless the deployment of keepalive is made into a highly available scenario). 2, the cluster is composed of n database server, the data write and query is rando
# The random password set for the root user at Thu Jul 16:23:52 (local time): Geeuu0krfqkatly0Log in to MySQL using the default password:Mysql-uroot-p geeuu0krfqkatly0Set the new root password, assuming that it is set to 111111mysql> SET PASSWORD = PASSWORD (' 111111 ');Set the root user login permission so that users can log on remotely using the client:mysql> use MySQL;
Mysql replication function-"master-slave" structure bitsCN.com
Mysql replication function-"master-slave" structure
1. configure the master server
1. add content in my. ini
2. create an account with "copy permission"
Create an account
Grant all operation permissions on the database to be copied to the created accou
The last time I configured the master-slave replication for mysql was at the beginning of the year, I did not expect to start using mysql again. Not much said, enter the main question Master-Slave build environment: Master: OS: rhel-server-63-x86_64Mysql: MySQL-5535-1 virtua
The benefits of using MySQL master-slave replication are:
1, the use of the master-slave server architecture, stability can be improved. If the primary server fails, we can use the server to provide services;2, in the master and slave server separately processing user's request, may enhance the data processing efficiency;3. Copy the data from the primary server to the server to protect the data from accide
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.