修改服务节点my.cnf,这里做临时配置,最终生效要配置到my.cnfMySQL [(none)]> set global relay_log_purge=0;Query OK, 0 rows affected (0.04 sec)MySQL [(none)]> grant all privileges on *.* to mha@'192.168.56.%' identified by '123456';Query OK, 0 rows affected, 1 warning (0.04 sec)MySQL [(none)]> flush privileges;Query OK, 0 rows affected (0.03 sec)配置如下:[client]port= 3306socket= /data/mysql/mysql.sock[mysql]no-auto-rehash[mysqld]user = mysqlport= 3306socket= /data/mysql/mysql.sockdatadir= /data/mysql/datalog-bin = /data/mysql/mysql-binserver-id = 6#skip-grant-tablesrelay_log_purge=0
4、管理节点配置MHA[root@linux-node1 ~]# mkdir /etc/mha[root@linux-node1 ~]# mkdir /var/log/mha/app1 -p[root@linux-node1 ~]# vim /etc/mha/app1.cnf[server default]manager_log=/var/log/mha/app1/manager.log#设置manager的日志manager_workdir=/var/log/mha/app1.log#设置manager的工作目录master_binlog_dir=/data/mysql/data#设置master 保存binlog的位置,以便MHA可以找到master的日志user=mha#设置监控用户mhapassword=123456#设置mysql中root用户的密码,这个密码是前文中创建监控用户的那个密码ping_interval=2#设置监控主库,发送ping包的时间间隔,默认是3秒,尝试三次没有回应的时候自动进行railoverrepl_password=123456#设置复制用户的密码repl_user=rep#设置复制环境中的复制用户名ssh_user=root#设置ssh的登录用户名[server1]hostname=192.168.56.11port=3306[server2]candidate_master=1#设置为候选master,如果设置该参数以后,发生主从切换以后将会将此从库提升为主库,即使这个主库不是集群中事件最新的slavecheck_repl_delay=0#默认情况下如果一个slave落后master 100M的relay logs的话,MHA将不会选择该slave作为一个新的master,因为对于这个slave的恢复需要花费很长时间,通过设置check_repl_delay=0,MHA触发切换在选择一个新的master的时候将会忽略复制延时,这个参数对于设置了candidate_master=1的主机非常有用,因为这个候选主在切换的过程中一定是新的masterhostname=192.168.56.12port=3306[server3]hostname=192.168.56.13port=3306
5、配置SSH登录[root@linux-node1 ~]# ssh-keygen -t rsassh-copy-id -i .ssh/id_rsa.pub root@192.168.56.11ssh-copy-id -i .ssh/id_rsa.pub root@192.168.56.12ssh-copy-id -i .ssh/id_rsa.pub root@192.168.56.13[root@linux-node1 ~]# ssh 192.168.56.12Last login: Tue Jan9 17:03:24 2018 from 192.168.56.1[root@linux-node2 ~]# logoutConnection to 192.168.56.12 closed.[root@linux-node1 ~]# ssh 192.168.56.13Last login: Tue Jan9 21:25:59 2018 from 192.168.56.1[root@linux-node3 ~]# logoutConnection to 192.168.56.13 closed.[root@linux-node1 ~]# ssh 192.168.56.11Last failed login: Wed Jan 10 17:08:07 CST 2018 from linux-node2 on ssh:nottyThere were 3 failed login attempts since the last successful login.Last login: Sat Jan6 08:52:06 2018 from 192.168.56.1[root@linux-node1 ~]# logoutConnection to 192.168.56.11 closed.
6、检查SSH登录[root@linux-node1 ~]# masterha_check_ssh --conf=/etc/mha/app1.cnf Wed Jan 10 17:11:00 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Wed Jan 10 17:11:00 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..Wed Jan 10 17:11:00 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..Wed Jan 10 17:11:00 2018 - [info] Starting SSH connection tests..Wed Jan 10 17:11:03 2018 - [debug] Wed Jan 10 17:11:00 2018 - [debug]Connecting via SSH from root@192.168.56.11(192.168.56.11:22) to root@192.168.56.12(192.168.56.12:22)..Wed Jan 10 17:11:01 2018 - [debug]ok.Wed Jan 10 17:11:01 2018 - [debug]Connecting via SSH from root@192.168.56.11(192.168.56.11:22) to root@192.168.56.13(192.168.56.13:22)..Wed Jan 10 17:11:02 2018 - [debug]ok.Wed Jan 10 17:11:03 2018 - [debug] Wed Jan 10 17:11:01 2018 - [debug]Connecting via SSH from root@192.168.56.12(192.168.56.12:22) to root@192.168.56.11(192.168.56.11:22)..Wed Jan 10 17:11:02 2018 - [debug]ok.Wed Jan 10 17:11:02 2018 - [debug]Connecting via SSH from root@192.168.56.12(192.168.56.12:22) to root@192.168.56.13(192.168.56.13:22)..Wed Jan 10 17:11:02 2018 - [debug]ok.Wed Jan 10 17:11:03 2018 - [debug] Wed Jan 10 17:11:02 2018 - [debug]Connecting via SSH from root@192.168.56.13(192.168.56.13:22) to root@192.168.56.11(192.168.56.11:22)..Wed Jan 10 17:11:02 2018 - [debug]ok.Wed Jan 10 17:11:02 2018 - [debug]Connecting via SSH from root@192.168.56.13(192.168.56.13:22) to root@192.168.56.12(192.168.56.12:22)..Wed Jan 10 17:11:03 2018 - [debug]ok.Wed Jan 10 17:11:03 2018 - [info] All SSH connection tests passed successfully.
7、检查mysql replication是否配置成功[root@linux-node1 ~]# ln -s /usr/local/mysql/bin/mysql /usr/bin/mysql[root@linux-node1 ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/bin/mysqlbinlog#必须要做软连接,或者添加到PATH环境变量,否则会报错ot@linux-node1 ~]# masterha_check_repl --conf=/etc/mha/app1.cnf MySQL Replication Health is OK.
推荐阅读
- MySQL中的行级锁,表级锁,页级锁
- 霍山黄芽之瓦坛贮存法,如何用金属罐贮存霍山黄芽
- 快手早餐之鸡蛋葱油饼的做法
- 我想种植黄茶在哪里购买黄茶苗,中国黄茶之乡在哪里
- 黄茶的独特性表现在哪里呢,中国黄茶之乡在哪里
- 岳阳黄茶产自哪里,中国黄茶之乡在哪里
- 小风暴之时间的玫瑰郑婉莹结局 小风暴之时间的玫瑰高山的仇人是谁
- 十大名茶之六安瓜片的简述
- 茶道与茶艺,茶文化知识之茶艺
- 如果是MySQL引起的CPU消耗过大,你会如何优化?