Release Notes
Announcements
log_bin variable must be set to ON.binlog_format variable must be set to ROW.binlog_row_image must be set to FULL.gtid_mode can only be set to ON or OFF. We recommend that you set it to ON, because if it is set to OFF, an alarm will be triggered, and if it is set to ON_PERMISSIVE or OFF_PERMISSIVE, an error will be reported.server_id parameter must be set manually and cannot be 0.do_db and ignore_db.log_slave_updates variable must be set to ON.log_bin controls the binlog switch. You need to enable binlog to log all database table structure and data changes.my.cnf configuration file of the source database as follows:log_bin parameter only takes effect after the database is restarted. Therefore, if errors are also reported for the binlog_format, server_id, binlog_row_imageandexpire_logs_days` parameters in the verification stage, we recommend that you modify all these parameters before restarting the database so that all the modifications can take effect.my.cnf configuration file is /etc/my.cnf, subject to the actual conditions.log_bin = MYSQL_BINbinlog_format = ROWserver_id = 2 //We recommend that you set it to an integer above 1. The value here is only an examplebinlog_row_image = FULLexpire_logs_days = 3 //Modify the binlog retention period (at least 3 days preferably).
[$Mysql_Dir]/bin/mysqladmin -u root -p shutdown[$Mysql_Dir]/bin/safe_mysqld &
show variables like '%log_bin%';
mysql> show variables like '%log_bin%';+------------------+-------+| Variable_name | Value |+------------------+-------+| log_bin | ON |+------------------+-------+| binlog_format | ROW |+------------------+-------+| binlog_row_image | FULL |+------------------+-------+1 row in set (0.00 sec)
binlog_format parameterbinlog_format specifies one of the following three binlog formats:STATEMENT: Each SQL statement that modifies the data will be logged into the binlog of the source/primary database. When replicating data, the replica/secondary database will run the same SQL statements as those in the source/primary database. This format can reduce the binlog size. However, the replica/secondary database may not be able to properly replicate certain functions.ROW: The binlog will log the modification of each data row, and the replica/secondary database will modify the same data. This format guarantees the correct source-replica or primary-secondary replication, but the binlog size will increase.MIXED: It is a combination of the above two formats. MySQL will automatically select STATEMENT or ROW format to log each executed SQL statement.binlog_format parameter should be set to ROW. If a similar error occurs, fix it as follows:binlog_format.set global binlog_format = ROW;
show variables like '%binlog_format%';
mysql> show variables like '%binlog_format%';+---------------+-------+| Variable_name | Value |+---------------+-------+| binlog_format | ROW |+---------------+-------+1 row in set (0.00 sec)
binlog_row_image parameterbinlog_row_image parameter determines how the binlog logs the pre-image (content before modification) and post-image (content after modification), which directly affects features such as data flashback and source-replica or primary-replica replication.
The binlog_row_image parameter takes effect only if binlog_format is set to ROW. The following describes the effects of specific values:FULL: In ROW format, binlog will log all the pre-image and post-image column data information.MINIMAL: In ROW format, if a table has no primary key or unique key, the pre-image will log all columns, and the post-image will log the modified columns. If it has a primary key or unique key, both the pre-image and post-image will only log the affected columns.binlog_row_image to FULL to make the source database binlog log the full image. If an error occurs, troubleshoot as follows:binlog_row_image:set global binlog_row_image = FULL;
show variables like '%binlog_row_image%';
mysql> show variables like '%binlog_row_image%';+------------------+-------+| Variable_name | Value |+------------------+-------+| binlog_row_image | FULL |+------------------+-------+1 row in set (0.00 sec)
gtid_mode parametergtid_mode to ON or OFF. We recommend that you set it to ON; otherwise, an alarm will be triggered during verification.gtid_mode. When modifying the value, you can only do so in the specified sequence step by step; for example, if you want to change OFF to ON, you should modify the gtid_mode value in the following sequence: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON.OFF: All new transactions in the source/primary database and all transactions in the replica/secondary database must be anonymous.OFF_PERMISSIVE: All new transactions in the source/primary database must be anonymous. Transactions in the replica/secondary database can be anonymous or GTID transactions but cannot only be GTID transactions.ON_PERMISSIVE: All new transactions in the source/primary database must be GTID transactions, and transactions in the replica/secondary database can be anonymous or GTID transactions.ON: All new transactions in the source/primary database and all transactions in the replica/secondary database must be GTID transactions.gtid_mode = OFF_PERMISSIVE on the source/primary and replica databases.
On MySQL versions earlier than v5.7.6, you need to modify the parameter in the my.cnf configuration file and restart the database to make the change take effect. On v5.7.6 and later, you can modify the parameter through global naming without restarting the database, but you must reset all business connections.set global gtid_mode = OFF_PERMISSIVE;
gtid_mode = ON_PERMISSIVE on the source/primary and replica databases.set global gtid_mode = ON_PERMISSIVE;
0, the consumption is completed.show variables like '%ONGOING_ANONYMOUS_TRANSACTION_COUNT%';
mysql> show variables like '%ONGOING_ANONYMOUS_TRANSACTION_COUNT%';+-------------------------------------+-------+| Variable_name | Value |+-------------------------------------+-------+| Ongoing_anonymous_transaction_count | 0 |+-------------------------------------+-------+1 row in set (0.00 sec)
gtid_mode = ON on the source/primary and replica databases.set global gtid_mode = ON;
my.cnf file and restart the database to make the initial values take effect.my.cnf configuration file is /etc/my.cnf, subject to the actual conditions.gtid_mode = onenforce_gtid_consistency = on
server_id parameterserver_id parameter must be set manually and cannot be 0. The default value of this parameter is 1, but the configuration may not be correct even if the queried parameter value is 1. You still need to set it manually.server_id:set global server_id = 2; // We recommend that you set it to an integer above 1. The value here is only an example.
show global variables like '%server_id%';
mysql> show global variables like '%server_id%';+---------------+-------+| Variable_name | Value |+---------------+-------+| server_id | 2 |+---------------+-------+1 row in set (0.00 sec)
do_db and ignore_db settingsdo_db and ignore_db are used to set the filter conditions for binlog.binlog_do_db: Only the specified databases will be logged in the binlog (all databases will be logged by default).binlog_ignore_db: The specified databases will not be logged in the binlog.do_db and ignore_db are set, some cross-database operations will not be logged in the binlog, and source-replica or primary-replica replication will be abnormal; therefore, this setting is not recommended. If a similar error occurs, fix it as follows:my.cnf configuration file in the source database to delete do_db and ignore_db settings.my.cnf configuration file is /etc/my.cnf, subject to the actual conditions.[$Mysql_Dir]/bin/mysqladmin -u root -p shutdown[$Mysql_Dir]/bin/safe_mysqld &
show master status;
mysql> show master status;+---------------+----------+--------------+------------------+-------------------+| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |+---------------+----------+--------------+------------------+-------------------+| binlog.000011 | 154 | | | |+---------------+----------+--------------+------------------+-------------------+
log_slave_updates parameterlog-bin parameter is enabled in the replica/secondary database, data operations directly performed in this database can be logged in the binlog, but data replications from the source/primary database to the replica/secondary database cannot be logged. Therefore, if the replica/secondary database is to be used as the source/primary database of another database, the log_slave_updates parameter needs to be enabled.my.cnf configuration file of the source database.my.cnf configuration file is /etc/my.cnf, subject to the actual conditions.log_slave_updates = ON
[$Mysql_Dir]/bin/mysqladmin -u root -p shutdown[$Mysql_Dir]/bin/safe_mysqld &
show variables like '%log_slave_updates%';
mysql> show variables like '%log_slave_updates%';+-------------------+-------+| Variable_name | Value |+-------------------+-------+| log_slave_updates | ON |+-------------------+-------+1 row in set (0.00 sec)
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan