percona-xtradb-cluster启动与写同步问题,从节点写入数据无法同步到主节点

GraceLingling 2015-07-27 07:20:34
安装环境与配置:
环境:virtualbox
OS:redhat6.3
服务器数量:3个,分别为node1,node2,node3
IP:192.168.0.213,192.168.0.214,192.168.0.215

问题描述:pxc套件安装完成后,主节点顺利开启,但从节点一直启不来,查日志发现SST出问题了。innobackup.backup.log错误日志提示innobackupex: Error: Failed to connect to MySQL server as DBD::mysql module is not installed at /usr//bin/innobackupex line 3006. 尝试各种方法,后来试着将my.cnf中wsrep_sst_method 由xtrabackup-v2 改为rsync就好了,再改回来也可以。但是使用过程中发现,在node1节点写入数据时数据立即被同步到其他节点,而在node2/node3节点写入数据,则无法同步到其余节点,一直搞不明白是什么原因,请各位大神指教啊。。。。小女在此谢过~~~

附三个节点的配置文件和错误日志:
my.cnf
node1
[mysqld]
# basic settings
datadir = /opt/mysql/data
tmpdir = /opt/mysql/tmp
socket = /opt/mysql/run/mysqld.sock
port = 3306
pid-file = /opt/mysql/run/mysqld.pid
skip-external-locking
max_allowed_packet = 16M
# innodb settings
default-storage-engine = INNODB
innodb_file_per_table = 1
log-bin = /opt/mysql/binlogs/bin-log-mysqld
log-bin-index = /opt/mysql/binlogs/bin-log-mysqld.index
innodb_data_home_dir = /opt/mysql/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /opt/mysql/data
#binlog-do-db = testdb
# xtradb cluster settings
binlog_format = ROW
wsrep_cluster_name = mycluster
wsrep_cluster_address = gcomm://192.168.0.213,192.168.0.214,192.168.0.215
wsrep_node_address = 192.168.0.213
wsrep_node_name=node_1
wsrep_provider = /usr/lib64/libgalera_smm.so
wsrep_sst_method = rsync
#xtrabackup-v2 rsync
wsrep_sst_auth = sstuser:sstuser123456
innodb_locks_unsafe_for_binlog = 1
innodb_autoinc_lock_mode = 2
# server id
server-id=1
# other settings
[mysqld_safe]
log-error = /opt/mysql/log/mysqld.log
pid-file = /opt/mysql/run/mysqld.pid
open-files-limit = 8192
[mysqlhotcopy]
interactive-timeout
[client]
port = 3306
socket = /opt/mysql/run/mysqld.sock
default-character-set = utf8

node2不同部分
wsrep_node_address = 192.168.0.214
wsrep_node_name=node_2
server-id=2

node3不同部分
wsrep_node_address = 192.168.0.215
wsrep_node_name=node_3
server-id=3

node1错误日志
WSREP_SST: [ERROR] innobackupex finished with error: 1. Check /opt/mysql/data//innobackup.backup.log (20150724 19:15:27.959)
WSREP_SST: [ERROR] Cleanup after exit with status:22 (20150724 19:15:27.961)
WSREP_SST: [INFO] Cleaning up temporary directories (20150724 19:15:27.962)
150724 19:15:27 [ERROR] WSREP: Failed to read from: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.0.170:4444/xtrabackup_sst' --auth 'sstuser:sstuser123456' --socket '/opt/mysql/run/mysqld.sock' --datadir '/opt/mysql/data/' --defaults-file '/etc/my.cnf' --gtid '453d2d43-3127-11e5-934c-6f001025a754:10'
150724 19:15:27 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.0.170:4444/xtrabackup_sst' --auth 'sstuser:sstuser123456' --socket '/opt/mysql/run/mysqld.sock' --datadir '/opt/mysql/data/' --defaults-file '/etc/my.cnf' --gtid '453d2d43-3127-11e5-934c-6f001025a754:10': 22 (Invalid argument)
150724 19:15:27 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.0.170:4444/xtrabackup_sst' --auth 'sstuser:sstuser123456' --socket '/opt/mysql/run/mysqld.sock' --datadir '/opt/mysql/data/' --defaults-file '/etc/my.cnf' --gtid '453d2d43-3127-11e5-934c-6f001025a754:10'
150724 19:15:27 [Warning] WSREP: 0 (node_213): State transfer to 1 (node_170) failed: -22 (Invalid argument)
150724 19:15:27 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 10)
150724 19:15:28 [Note] WSREP: forgetting ff0be51d (tcp://192.168.0.170:4567)
150724 19:15:28 [Note] WSREP: Node eee80315 state prim
150724 19:15:28 [Note] WSREP: forgetting ff0be51d (tcp://192.168.0.170:4567)
150724 19:15:28 [Note] WSREP: Member 0 (node_213) synced with group.
150724 19:15:28 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 10)
150724 19:15:28 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1
150724 19:15:28 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 4a685b6a-31f5-11e5-9b6f-2bb53d3e41c2
150724 19:15:28 [Note] WSREP: STATE EXCHANGE: sent state msg: 4a685b6a-31f5-11e5-9b6f-2bb53d3e41c2
150724 19:15:28 [Note] WSREP: STATE EXCHANGE: got state msg: 4a685b6a-31f5-11e5-9b6f-2bb53d3e41c2 from 0 (node_213)
150724 19:15:28 [Note] WSREP: Quorum results:
version = 2,
component = PRIMARY,
conf_id = 6,
members = 1/1 (joined/total),
act_id = 10,
last_appl. = 0,
protocols = 0/4/3 (gcs/repl/appl),
group UUID = 453d2d43-3127-11e5-934c-6f001025a754
150724 19:15:28 [Note] WSREP: Flow-control interval: [16, 16]
150724 19:15:28 [Note] WSREP: Synchronized with group, ready for connections
150724 19:15:28 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
150724 19:15:28 [Note] WSREP: New cluster view: global state: 453d2d43-3127-11e5-934c-6f001025a754:10, view# 7: Primary, number of nodes: 1, my index: 0, protocol version 3
150724 19:15:28 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
150724 19:15:28 [Note] WSREP: Assign initial position for certification: 10, protocol version: 2
150724 19:15:34 [Note] WSREP: cleaning up ff0be51d (tcp://192.168.0.170:4567)
150724 19:16:47 [Note] /usr/sbin/mysqld: Normal shutdown
innobackup.backup.log

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

150724 19:15:27 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/etc/my.cnf;mysql_read_default_group=xtrabackup;mysql_socket=/opt/mysql/run/mysqld.sock' as 'sstuser' (using password: YES).
innobackupex: got a fatal error with the following stacktrace: at /usr//bin/innobackupex line 3006
main::mysql_connect('abort_on_error', 1) called at /usr//bin/innobackupex line 1570
innobackupex: Error: Failed to connect to MySQL server as DBD::mysql module is not installed at /usr//bin/innobackupex line 3006.
...全文
470 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
qq_33228589 2016-12-14
  • 打赏
  • 举报
回复
你好,你的错误解决了吗?我也遇到同样的问题啊
GraceLingling 2015-08-03
  • 打赏
  • 举报
回复
引用 2 楼 GUANYIJUN123 的回复:
好像,论坛的mysql比较冷,没有什么人 没有玩过percona-xtradb-cluster,直接去baidu(google)查找一下错误日志的内容看看!
百度了N回了也没啥结果。要不也不来这发帖子了。。。。
迷途的书童 2015-08-03
  • 打赏
  • 举报
回复
好像,论坛的mysql比较冷,没有什么人 没有玩过percona-xtradb-cluster,直接去baidu(google)查找一下错误日志的内容看看!
GraceLingling 2015-07-29
  • 打赏
  • 举报
回复
咋没人理我。。自己顶顶

56,675

社区成员

发帖
与我相关
我的任务
社区描述
MySQL相关内容讨论专区
社区管理员
  • MySQL
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧