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

Create a new pxc001 server:

System: centos7

Memory: 2G

Disk: 128G

IP address: 192.168.0.201 (first node)

192.168.0.202

192.168.0.203

# vi / etc/selinux/config

SELINUX=disabled # change this item to disabled

# execute the command setenforce 0

# systemctl restart firewalld

Open the four ports of the firewall

Firewall-cmd-add-port=4444/tcp-permanent

Firewall-cmd-add-port=4567/tcp-permanent

Firewall-cmd-add-port=4568/tcp-permanent

Firewall-cmd-add-port=3306/tcp-permanent

Install the cluster

# yum-y install http://www.percona.com/downloads/percona-release/redhat/0.1-4/percona-release-0.1-4.noarch.rpm

# yum-y update percona-release

# yum-y install Percona-XtraDB-Cluster-57

Start mysql and change the password

Service mysql startgrep 'temporary password' / var/log/mysqld.log

[Note] A temporary password is generated for root@localhost: u8Eten Morel pendant Tech.

# mysql-uroot-pu8E;M:,p_T&H

Mysql > update mysql.user set authentication_string=password ('BingoData@1024.com') where user='root' and Host =' localhost'

Start the first machine (201 server) in the following way, which is called the boot node.

This is the only one that starts in this way. Other servers are started with service mysql start

# ssh 192.168.0.201

# systemctl start mysql@bootstrap.service

Enter mysql

# mysql-uroot-pBingoData@1024.com

# set wsrep_causal_reads = 1; to avoid data inconsistency among nodes, you need to wait for full synchronous replication to copy this file to master1 and master2, and pay attention to changing wsrep_node_name and wsrep_node_address to hostname and ip of the corresponding nodes.

Create the IP of all nodes corresponding to the user in the profile to create

# mysql-uroot-pBingoData@1024.com

Mysql > grant all privileges on. To 'pxcuser'@'%' identified by' BingoData@1024.com'

The error is as follows:

ERROR 1820 (HY000): You must reset your password using ALTER USER statement before executing this statement.

Solution:

Mysql > set password = password ('BingoData@1024.com')

Mysql > grant all privileges on. To 'pxcuser'@'%' identified by' BingoData@1024.com'

Mysql > grant all privileges on. To 'pxcuser'@'localhost' identified by' BingoData@1024.com'

Mysql > flush privileges

Enter 202 and 203 server configuration

# ssh 192.168.0.203

Pay attention to the startup mode of 203 and 202

# service mysql start

Create the IP of all nodes corresponding to the user in the profile to create

Mysql > grant all privileges on. To 'pxcuser'@'%' identified by' BingoData@1024.com'

Mysql > grant all privileges on. To 'pxcuser'@'localhost' identified by' BingoData@1024.com'

Mysql > flush privileges

Note: the start and stop of services should correspond

Service mysql stop-> use service mysql start at startup

Systemctl stop mysql@bootstrap.service-> enabled with systemctl start mysql@bootstrap.service

Pay attention to avoid the pit: the server with safe_to_bootstrap 1 in the / var/lib/mysql/grastate.dat file is the main library, start it as the main library! We can also set up the server manually by who we want to be the master database, and the uuid of the three clusters is the same before starting.

A seqno of-1 means that you have joined the cluster, and the seqno will change after the database is shut down.

After the following server 201 is started as the main library, seqno has changed from 4 to-1, indicating that it has joined the cluster.

203 server has been unable to start as a slave library.

The startup method is: service mysql start

The error message is as follows # tail-fn 100 / var/log/mysqld.log

2020-01-10T09:25:56.982598Z 0 [Note] WSREP: (32d9017e, 'tcp://0.0.0.0:4567') turning message relay requesting off

2020-01-10T09:26:23.489499Z 0 [Note] WSREP: (32d9017e, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers: tcp://192.168.0.202:4567

2020-01-10T09:26:24.489792Z 0 [Note] WSREP: (32d9017e, 'tcp://0.0.0.0:4567') reconnecting to 30d8eb06 (tcp://192.168.0.202:4567), attempt 0

2020-01-10T09:26:24.494967Z 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view (pc.wait_prim_timeout): 110 (Connection timed out)

At gcomm/src/pc.cpp:connect (): 159

2020-01-10T09:26:24.495007Z 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open (): 209: Failed to open backend connection:-110 (Connection timed out)

2020-01-10T09:26:24.495376Z 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open (): 1514: Failed to open channel 'pxc-cluster-test' at' gcomm://192.168.0.202192.168.0.203192.168.0.201':-110 (Connection timed out)

2020-01-10T09:26:24.495402Z 0 [ERROR] WSREP: gcs connect failed: Connection timed out

2020-01-10T09:26:24.495415Z 0 [ERROR] WSREP: Provider/Node (gcomm://192.168.0.202192.168.0.203192.168.0.201) failed to establish connection with cluster (reason: 7)

2020-01-10T09:26:24.495423Z 0 [ERROR] Aborting

Solution: change the uuid of the grastate.dat file of the 203server to exactly the same as 202201 and you can start it.

Safe_to_bootstrap: set to 0

So what is UUID?

Why is the UUID of the same pxc cluster the same?

Verify the cluster: show status like 'wsrep%'

| | wsrep_incoming_addresses | 192.168.0.202VR 3306192.168.0.203VRO 3306192.168.0.201VOR 3306 |

| | wsrep_cluster_weight | 3 | |

| | wsrep_desync_count | 0 | |

| | wsrep_evs_delayed |

| | wsrep_evs_evict_list |

| | wsrep_evs_repl_latency | 0 / 0 / 0 | 0 / 0 / 0 |

| | wsrep_evs_state | OPERATIONAL |

| | wsrep_gcomm_uuid | e9e76881-338f-11ea-90d6-3b07eeeaf3a4 |

| | wsrep_cluster_conf_id | 3 | |

| | wsrep_cluster_size | 3 | |

| | wsrep_cluster_state_uuid | 9d5bc8a5-3374-11ea-9aac-b3599f4e37e4 |

| | wsrep_cluster_status | Primary |

| | wsrep_connected | ON |

| | wsrep_local_bf_aborts | 0 | |

| | wsrep_local_index | 2 | |

| | wsrep_provider_name | Galera |

| | wsrep_provider_vendor | Codership Oy |

| | wsrep_provider_version | 3.41 (rb3295e6) |

| | wsrep_ready | ON |

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.