Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "the installation steps of MYSQL MGR". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

# required parameters for MGR #

Server_id=1

Gtid_mode=ON

Enforce_gtid_consistency=ON

Master_info_repository=TABLE

Relay_log_info_repository=TABLE

Log_slave_updates=ON

Log_bin=binlog

Binlog_format=ROW

Binlog_checksum=NONE

Transaction_write_set_extraction=XXHASH64

Loose-group_replication_group_name= "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"

Loose-group_replication_start_on_boot=off

Loose-group_replication_local_address= "10.10.203.147purl 24901"

Loose-group_replication_group_seeds= "10.10.203.145VOR 24901Magne10.10.203.146VOL24901JI 10.10.203.147Rod 24901"

Loose-group_replication_bootstrap_group= off

# for performance_schema

Performance_schema = on

Performance_schema_consumer_events_stages_current=on

Performance_schema_consumer_events_stages_history=on

Performance_schema_consumer_events_stages_history_long=off

Performance_schema_consumer_statements_digest=on

Performance_schema_consumer_events_statements_current=on

Performance_schema_consumer_events_statements_history=on

Performance_schema_consumer_events_statements_history_long=off

Performance_schema_consumer_events_waits_current=on

Performance_schema_consumer_events_waits_history=on

Performance_schema_consumer_events_waits_history_long=off

Performance_schema_consumer_global_instrumentation=on

Performance_schema_consumer_thread_instrumentation=on

# MYSQL CMD##

SET SQL_LOG_BIN=0

CREATE USER rpl_user@'%' IDENTIFIED BY '123456'

GRANT REPLICATION SLAVE ON *. * TO rpl_user@'%'

FLUSH PRIVILEGES

SET SQL_LOG_BIN=1

CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='123456' FOR CHANNEL 'group_replication_recovery'

INSTALL PLUGIN group_replication SONAME 'group_replication.so';-you don't have to execute it after the first installation

SET GLOBAL group_replication_bootstrap_group=ON;-only machines that act as SEED nodes are used, otherwise all nodes default to SEED nodes, pits

Set global group_replication_allow_local_disjoint_gtids_join=1;-- executed only on slave nodes

START GROUP_REPLICATION

SET GLOBAL group_replication_bootstrap_group=OFF

SELECT * FROM performance_schema.replication_group_members

Select * from performance_schema.replication_connection_status\ G

CREATE DATABASE test

Use test

CREATE TABLE T1 (C1 INT PRIMARY KEY, c2 TEXT NOT NULL)

INSERT INTO T1 VALUES (1, 'Luis')

SHOW BINLOG EVENTS

Show global status like'% group_replication_primary%'

Limitations of MGR

Only InnoDB tables are supported, and each table must have a primary key for conflict detection of write set.

The GTID feature must be turned on, and the binary log format must be set to ROW, which is used to select master and write set.

COMMIT may cause failures, similar to failure scenarios at snapshot transaction isolation level

Currently, a MGR cluster supports up to 9 nodes.

Does not support foreign keys in save point features, can not do global constraint detection and partial rollback

Binary log does not support binlog event checksum

Error resolution:

# # 2018-07-10T06:17:00.054571Z 41 [ERROR] Slave I retry-time O for channel 'group_replication_recovery': error connecting to master' rpl_user@mha-slave1:3307'-retry-time: 60 retries: 1, Error_code: 2005

There is a problem with IP parsing in / etc/hosts, which is normal after modification.

This is the end of the content of "MYSQL MGR installation steps". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.