Shulou(Shulou.com)06/01 Report--

MySQL Group Replication installation

192.168.10.65

192.168.10.66

192.168.10.67

OS: CentOS 7.4

Mysql soft: 8.0.12

Install MySQL and create an instance

Refer to the mysql8.0.12 source code installation here

2. Several specified parameters of mgr are added to the configuration file, and the restart takes effect.

-- profile

Binlog_format = ROW

Gtid_mode = ON

Enforce_gtid_consistency = ON

Log_slave_updates = ON

Master_info_repository = TABLE

Relay_log_info_repository = TABLE

Binlog_checksum = NONE

Transaction_write_set_extraction = XXHASH64 # enable the primary key information collection function. The default value is XXHASH64 since 8.0.2

Loose-group_replication_group_name = "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" # set the group name at will, but cannot repeat it with UUID

Loose-group_replication_start_on_boot = OFF # # set to OFF to avoid automatically booting a second group with the same name every time you start.

Loose-group_replication_bootstrap_group = OFF # ditto

Loose-group_replication_local_address = "192.168.10.65 24901" # set the local address of the member, and change it to the corresponding IP address for different nodes.

Loose-group_replication_group_seeds = "192.168.10.65 virtual 24901192.168.10.66 virtual 24902192.168.10.67 24903" # set the address of the seed member

Loose-group_replication_single_primary_mode = FALSE # build multi-master mode

Loose-group_replication_enforce_update_everywhere_checks = ON # avoid undetected foreign key conflicts

-- set the whitelist and choose to do

Loose-global group_replication_ip_whitelist= "192.168.10.65192.168.10.66192.168.10.67"

Loose-global group_replication_ip_whitelist= "127.0.0.1Universe 10.0.0.0Compare 8172.16.0.0Universe 12192.168.0.0According to 16192.168.1.0 Universe 24"

Third, operate the first node

-- install plug-ins

Mysql > INSTALL PLUGIN group_replication SONAME 'group_replication.so'

-- to create a user, be careful not to record it in the binlog file

Mysql > SET SQL_LOG_BIN=0; # create authorized users without writing to bin_log

Mysql > CREATE USER 'repl'@'192.168.%' identified by' repl'

Mysql > GRANT REPLICATION SLAVE ON. TO 'repl'@'192.168.%'

Mysql > flush privileges

Mysql > SET SQL_LOG_BIN=1

This sentence has only the first node, which is executed when the boot group is executed for the first time. A restart is also needed. Shut down after starting group_replication.

Mysql > SET GLOBAL group_replication_bootstrap_group=ON

Mysql > CHANGE MASTER TO MASTER_USER='repl',MASTER_PASSWORD='repl' FOR CHANNEL 'group_replication_recovery'

-- start

Mysql > START GROUP_REPLICATION

Mysql > SET GLOBAL group_replication_bootstrap_group=OFF

-- check the current mgr members to determine whether the first node is successful. The member_state status must be ONLINE.

Mysql > SELECT * FROM performance_schema.replication_group_members

Fourth, operate the second and third nodes

-- install plug-ins

Mysql > INSTALL PLUGIN group_replication SONAME 'group_replication.so'

-- to create a user, be careful not to record it in the binlog file

Mysql > SET SQL_LOG_BIN=0; # create authorized users without writing to bin_log

Mysql > CREATE USER 'repl'@'192.168.%' identified by' repl'

Mysql > GRANT REPLICATION SLAVE ON. TO 'repl'@'192.168.%'

Mysql > flush privileges

Mysql > SET SQL_LOG_BIN=1

Mysql > CHANGE MASTER TO MASTER_USER='repl',MASTER_PASSWORD='repl' FOR CHANNEL 'group_replication_recovery'

-- start

Mysql > START GROUP_REPLICATION

Common errors:

Unable to connect to the port

2018-09-18T16:31:04.579403+08:00 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported:'[GCS] Unable to announce tcp port 3306. Port already in use?'

2018-09-18T16:31:04.579607+08:00 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported:'[GCS] Error joining the group while waiting for the network layer to become ready.'

2018-09-18T16:31:04.579741+08:00 0 [ERROR] [MY-011735] [Repl] Plugin group_replication reported:'[GCS] The member was unable to join the group. Local port: 3306'

2018-09-18T16:32:04.532459+08:00 8 [ERROR] [MY-011640] [Repl] Plugin group_replication reported: 'Timeout on wait for view after joining group'

2018-09-18T16:32:04.532736+08:00 8 [ERROR] [MY-011735] [Repl] Plugin group_replication reported:'[GCS] The member is leaving a group without being on one.'

Reason:

Loose-group_replication_local_address = "192.168.10.65 purl 3306"

Loose-group_replication_group_seeds = "192.168.10.65 Vol 3306192.168.10.66 Rd 3306192.168.10.67 Rd 3306"

There is a problem with the parameter setting. IP is not followed by port. According to the example on the official website, you can fill in 24901, 24902, and 24903 in sequence.

Solution:

Loose-group_replication_local_address = "192.168.10.65 purl 24901"

Loose-group_replication_group_seeds = "192.168.10.65 Vol 24901192.168.10.66 Rd 24902192.168.10.67 Rd 24903"

Second, errors caused by binlog

2018-09-18T16:45:44.394139+08:00 0 [ERROR] [MY-011526] [Repl] Plugin group_replication reported: 'This member has more executed transactions than t hose present in the group. Local transactions: 82ab7fe2-bb1c-11e8-a4ec-00505687bb25:1-11 > Group transactions: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa: 1-2'

2018-09-18T16:45:44.394256+08:00 0 [ERROR] [MY-011522] [Repl] Plugin group_replication reported: 'The member contains transactions not present in the group. The member will now exit the group.'

Reason:

When you create a user, record it in binlog, which is why you set the action not to be recorded in binlog when you create a user.

Solution:

The simple and rude approach is for each node to stop replication, reset master, and then start replication in sequence.

Stop group_replication

Reset master

Start group_replication

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.