mysql replication status

/MY.CNF (the configuration file in Windows is Mysql.ini)Log-bin=mysql-bin Open Binary LogNote: The binary log must be turned on because the synchronization of the data is essentially the other MySQL database server executes the binary log of this data change again on this computer.192.168.95.11 Primary database server192.168.95.12 from the database serverBack to top 3.3, start building master-slave replicat

. 2. Create an account dedicated to replication on the master: weidai/123456 The newly added account can be queried in the mysql. user table: During my first operation, the account was created here, but it was found that the account was not copied successfully, check whether the binlong generated by the master node is correct during troubleshooting. Then, check the slave

. Master-Slave Replication configuration steps: Set Server-id (server identity, which cannot be duplicated in a group of hosts) Turn on the binary log and specify the path to save the binary log file Record Bin-log files and bin-log (position) locations If you keep on master, add a global lock, backup the database that needs to be synchronized to the slave node, and unlock the global lock. Create a user for synchronous

= 2Auto_increment_offset = 1 Node B: Log-bin = mysql-binServer-id = 2Binlog-do-db = testBinlog-ignore-db = mysqlReplicate-do-db = testReplicate-ignore-db = mysqlLog-slave-updatesSync_binlog = 1Auto_increment_increment = 2Auto_increment_offset = 2 After the configuration is changed, you must start mysql before proceeding to the next step. Each AB node creates an account accessed by the other Party: Grant

, mutual authorized users (in a server authorized a user to allow B access, and vice versa)On Server A (192.168.1.254)Mysql> GRANT REPLICATION SLAVE on * * to ' mysync ' @ ' 192.168.1.252 ' identified by PASSWORD ' 123456 ';mysql> flush Privileges;On Server B (192.168.1.252)Mysql> GRANT

MySQL uses show status to view the status of the MySQL server, statusmysql During website development in the LAMP architecture, we sometimes need to know the MySQL server status information, such as the running time after

Build a MYSQL master-slave replication structure and a mysql master-slave replication Structure 1. Select two servers as the master and backup databases respectively. 2. log on to the server, Yum install mysql; Yum install mysql-s

Slave_ SQL _Running are No It indicates that the replication process has not started. The log location is 4 rather than 0, because 0 is the start position of the log file, not the log location. In fact, MySQL knows that the first event is located at 4. To start replication, you can run: Mysql> start slave; Run show sl

/mysql.sock4.3 Initialize master, slave all nodes, and start/application/mysql/scripts/mysql_install_db--basedir=/application/mysql--datadir=/application/mysql/data--user =mysql/etc/init.d/mysqld start4.4master Node Authorized user Replmysql> gant replication Slave on * * to

ArticleDirectory If MongoDB is just a document-type database, there is no bright spot. However, the biggest advantage of MongoDB is read extension, hot backup, fault recovery, and automatic sharding (write extension ). These functions will be introduced at the end of this series. 1. Status Monitoring 2. Backup and Replication 3. Automatic sharding If MongoDB is just a document-type dat

> Show databases;+--------------------+| database |+--------------------+| Information_schema | | mysql | | PErformance_schema | | sys | | test |+--------------------+5 rows in Set (0.00 sec) to slave data recovery Mys Ql> source/mysql/test3.sqlmysql> show databases;+--------------------+| database |+--------------------+| Information_schema | | m