深度遗忘
深度遗忘

MySQL半同步 + MHA架构配置文档

拓扑介绍：

192.168.43.141  Master

192.168.43.142  Slave01

192.168.43.143  Slave02

192.168.43.144  Mha-manager

                  vip   (192.168.43.145)   vip

            Master（主） --> Slave01(从、备主)

              |                                                                <- Mha-manager(monitor-MHA)   

              |- - -> Slave02（从）


OS    : CentOS release 6.10 (Final) Mini

Perl  : v5.10.1 x86_64-linux-thread-multi(系统版本自带)

Gateway : 192.168.43.1

MySQL   : mysql-5.7.31-1.el6.x86_64.rpm-bundle.tar

MHA       : mha4mysql-manager-0.56-0.el6.noarch.rpm

                   mha4mysql-node-0.56-0.el6.noarch.rpm

MHA官方github         ： https://github.com/yoshinorim/mha4mysql-manager/wiki

MySQL主从复制模式： 我们选用半同步机制

一、系统调整（所有节点）

1.修改/etc/hosts

[root@mha-manager ~]# cat /etc/hosts

127.0.0.1  localhost localhost.localdomain localhost4 localhost4.localdomain4

::1        localhost localhost.localdomain localhost6 localhost6.localdomain6

192.168.43.141  Master

192.168.43.142  Slave01

192.168.43.143  Slave02

192.168.43.144  Mha-manager

2.关闭防火墙及SELINUX

[root@mha-manager ~]# /etc/init.d/iptables stop

[root@mha-manager ~]# getenforce

Disabled

3.安装基本工具

[root@mha-manager ~]# yum install ntp vim wget net-tools mlocate openssh-* cc gcc make -y

二、安装MHA所需依赖（所有节点）

1.配置SSH免密登录

[root@ ~]# ssh-keygen -t rsa

[root@ ~]# for i in Master Slave01 Slave02 Mha-manager;do ssh-copy-id $i;done

2.测试免密登录

[root@ ~]# for i in Master Slave01 Slave02 Mha-manager;do ssh $i hostname;done

master

slave01

slave02

mha-manager

3.配置NTP服务器

[root@slave01 opt]# yum install ntp -y

[root@slave01 opt]# cat /etc/ntp.conf | grep 'server'

server ntp.aliyun.com

server ntp2.aliyun.com

[root@slave01 opt]# ntpdate ntp.aliyun.com

20 Aug 13:34:06 ntpdate[31767]: step time server 203.107.6.88 offset -1920.602438 sec

[root@slave01 opt]# date

Thu Aug 20 13:34:09 CST 2020

[root@slave01 opt]# /etc/init.d/ntpd start

Starting ntpd:                                            [  OK  ]

[root@slave01 opt]# chkconfig ntpd on

[root@slave01 opt]#

三、基于半同步的Mysql主从复制的安装

（一）半同步插件的安装与开启

0.安装mysql(所有数据库节点)

[root@slave01 opt]# tar -xf mysql-5.7.31-1.el6.x86_64.rpm-bundle.tar

[root@slave01 opt]# yum install -y mysql-community-*

1.启动MySQL，改修数据库root密码(所有数据库节点)

[root@master ~]# /etc/init.d/mysqld start

Initializing MySQL database:                              [  OK  ]

Starting mysqld:                                          [  OK  ]

mysql> alter user 'root'@'localhost' identified by 'Test.123';

Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;

Query OK, 0 rows affected (0.00 sec)

2.安装半同步插件(所有数据库节点)

（1）查找半同步所需插件

mysql> show variables like '%plugin_dir%';  #查找插件所在目录（每台DB服务器可能不一样）

+---------------+--------------------------+

| Variable_name | Value                    |

+---------------+--------------------------+

| plugin_dir    | /usr/lib64/mysql/plugin/ |

+---------------+--------------------------+

1 row in set (0.00 sec)

mysql> show variables like '%have_dynamic%';  #检查是否支持动态检测

+----------------------+-------+

| Variable_name        | Value |

+----------------------+-------+

| have_dynamic_loading | YES  |

+----------------------+-------+

1 row in set (0.01 sec)

mysql> system ls  /usr/lib64/mysql/plugin/ | egrep 'master|slave'

semisync_master.so

semisync_slave.so

（2）安装插件

mysql> install plugin rpl_semi_sync_master SONAME 'semisync_master.so';

Query OK, 0 rows affected (0.00 sec)

mysql> install plugin rpl_semi_sync_slave SONAME 'semisync_slave.so';

Query OK, 0 rows affected (0.00 sec)

（3）检查Plugin是否已正确安装

mysql> show plugins;

+----------------------------+----------+--------------------+----------------------+---------+

| Name                      | Status  | Type              | Library              | License |

+----------------------------+----------+--------------------+----------------------+---------+

| FEDERATED                  | DISABLED | STORAGE ENGINE    | NULL                | GPL    |

| ngram                      | ACTIVE  | FTPARSER          | NULL                | GPL    |

| validate_password          | ACTIVE  | VALIDATE PASSWORD  | validate_password.so | GPL    |

| rpl_semi_sync_master      | ACTIVE  | REPLICATION        | semisync_master.so  | GPL    |

| rpl_semi_sync_slave        | ACTIVE  | REPLICATION        | semisync_slave.so    | GPL    |

+----------------------------+----------+--------------------+----------------------+---------+

47 rows in set (0.00 sec)

mysql> show variables like '%rpl_semi_sync%';

+-------------------------------------------+------------+

| Variable_name                            | Value      |

+-------------------------------------------+------------+

| rpl_semi_sync_master_enabled              | OFF        |

| rpl_semi_sync_master_timeout              | 10000      |

| rpl_semi_sync_master_trace_level          | 32        |

| rpl_semi_sync_master_wait_for_slave_count | 1          |

| rpl_semi_sync_master_wait_no_slave        | ON        |

| rpl_semi_sync_master_wait_point          | AFTER_SYNC |

| rpl_semi_sync_slave_enabled              | OFF        |

| rpl_semi_sync_slave_trace_level          | 32        |

+-------------------------------------------+------------+

8 rows in set (0.01 sec)

mysql>

3.MySQL配置文件的修改

Master配置：

[root@master ~]# cat /etc/my.cnf

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

symbolic-links=0

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

server_id=1

log-bin=mysql-bin

binlog_format=mixed

rpl_semi_sync_master_enabled=1

rpl_semi_sync_master_timeout=1000

rpl_semi_sync_slave_enabled=1

relay_log_purge=0

relay-log = relay-bin

relay-log-index = slave-relay-bin.index

default-storage-engine = INNODB

character-set-server = utf8

collation-server = utf8_general_ci

relay_log_purge = 0

[client]

default-character-set = utf8

Slave01配置：

[root@slave01 ~]# cat /etc/my.cnf

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

symbolic-links=0

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

server_id=2

log-bin=mysql-bin

binlog_format=mixed

rpl_semi_sync_master_enabled=1

rpl_semi_sync_master_timeout=1000

rpl_semi_sync_slave_enabled=1

relay_log_purge=0

relay-log = relay-bin

relay-log-index = slave-relay-bin.index

default-storage-engine = INNODB

character-set-server = utf8

collation-server = utf8_general_ci

relay_log_purge = 0

Slave02配置：

#由于slave02只是用来做一个slave主机，所以无需开启master的半同步

[root@slave02 ~]# cat /etc/my.cnf

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

symbolic-links=0

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

server_id=3

log-bin = mysql-bin

relay-log = relay-bin

relay-log-index = slave-relay-bin.index

read_only = 1

rpl_semi_sync_slave_enabled=1

default-storage-engine = INNODB

character-set-server = utf8

collation-server = utf8_general_ci

relay_log_purge = 0

4.查看半同步状态是否开启

[root@ ~]# /etc/init.d/mysqld restart

Initializing MySQL database:                              [  OK  ]

Starting mysqld:                                          [  OK  ]

mysql> show variables like '%rpl_semi_sync%';

+-------------------------------------------+------------+

| Variable_name                            | Value      |

+-------------------------------------------+------------+

| rpl_semi_sync_master_enabled              | ON        |

| rpl_semi_sync_master_timeout              | 1000      |

| rpl_semi_sync_master_trace_level          | 32        |

| rpl_semi_sync_master_wait_for_slave_count | 1          |

| rpl_semi_sync_master_wait_no_slave        | ON        |

| rpl_semi_sync_master_wait_point          | AFTER_SYNC |

| rpl_semi_sync_slave_enabled              | ON        |

| rpl_semi_sync_slave_trace_level          | 32        |

+-------------------------------------------+------------+

8 rows in set (0.01 sec)

（二）配置主从复制

1.创建用户（Master上配置）

（1）插件主从复制同步用户

mysql> grant replication slave on *.* to mharep@'192.168.43.%' identified by 'Test.123';

Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show warnings\G;

*************************** 1. row ***************************

  Level: Warning

  Code: 1287

Message: Using GRANT statement to modify existing user's properties other than privileges is deprecated and will be removed in future release. Use ALTER USER statement for this operation.

1 row in set (0.00 sec)

（2）创建用户mha的manager监控的用户

mysql> grant all on *.* to manager@'192.168.43.%' identified by 'Test.123';

Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show warnings\G;

*************************** 1. row ***************************

  Level: Warning

  Code: 1287

Message: Using GRANT for creating new user is deprecated and will be removed in future release. Create new user with CREATE USER statement.

1 row in set (0.00 sec)

（3）查看master二进制相关的信息

mysql> show master status\G;

*************************** 1. row ***************************

            File: mysql-bin.000001

        Position: 1040

    Binlog_Do_DB:

Binlog_Ignore_DB:

Executed_Gtid_Set:

1 row in set (0.00 sec)

2.创建用户（Slave01上配置）

（1）创建用于同步的用户

mysql> grant replication slave on *.* to mharep@'192.168.43.%' identified by 'Test.123';

Query OK, 0 rows affected, 1 warning (1.00 sec)

（2）创建用户mha的manager监控的用户

mysql> grant all on *.* to manager@'192.168.43.%' identified by 'Test.123';

Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql>

3.创建用户（Slave02上配置）

由于slave02无需做备主，所以不用创建用于同步数据的账户

#创建manager监控账号

mysql> grant all on *.* to manager@'192.168.43.%' identified by 'Test.123';

Query OK, 0 rows affected, 1 warning (0.01 sec)

4.分别在Slave01与Slave02上执行：

Master上查日志文件和位置：

mysql> show master status\G;

*************************** 1. row ***************************

            File: mysql-bin.000001

        Position: 1040

    Binlog_Do_DB:

Binlog_Ignore_DB:

Executed_Gtid_Set:

1 row in set (0.00 sec)

Slave01上执行:

mysql> change master to master_host='192.168.43.141', master_port=3306, master_user='mharep',master_password='Test.123', master_log_file = 'mysql-bin.000001', master_log_pos=1040;

Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;

Query OK, 0 rows affected (0.02 sec)

mysql> show slave status\G;

*************************** 1. row ***************************

              Slave_IO_State: Waiting for master to send event

                  Master_Host: 192.168.43.141

                  Master_User: mharep

                  Master_Port: 3306

                Connect_Retry: 60

              Master_Log_File: mysql-bin.000001

          Read_Master_Log_Pos: 1040

              Relay_Log_File: relay-bin.000002

                Relay_Log_Pos: 320

        Relay_Master_Log_File: mysql-bin.000001

            Slave_IO_Running: Yes

            Slave_SQL_Running: Yes

              Replicate_Do_DB:

          Replicate_Ignore_DB:

          Replicate_Do_Table:

      Replicate_Ignore_Table:

      Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table:

                  Last_Errno: 0

                  Last_Error:

                Skip_Counter: 0

          Exec_Master_Log_Pos: 1040

              Relay_Log_Space: 521

              Until_Condition: None

              Until_Log_File:

                Until_Log_Pos: 0

          Master_SSL_Allowed: No

          Master_SSL_CA_File:

          Master_SSL_CA_Path:

              Master_SSL_Cert:

            Master_SSL_Cipher:

              Master_SSL_Key:

        Seconds_Behind_Master: 0

Master_SSL_Verify_Server_Cert: No

                Last_IO_Errno: 0

                Last_IO_Error:

              Last_SQL_Errno: 0

              Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

            Master_Server_Id: 1

                  Master_UUID: 6882c9b1-e23a-11ea-b7a9-000c29b26880

            Master_Info_File: /var/lib/mysql/master.info

                    SQL_Delay: 0

          SQL_Remaining_Delay: NULL

      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates

          Master_Retry_Count: 86400

                  Master_Bind:

      Last_IO_Error_Timestamp:

    Last_SQL_Error_Timestamp:

              Master_SSL_Crl:

          Master_SSL_Crlpath:

          Retrieved_Gtid_Set:

            Executed_Gtid_Set:

                Auto_Position: 0

        Replicate_Rewrite_DB:

                Channel_Name:

          Master_TLS_Version:

1 row in set (0.00 sec)

Slave02上执行:

mysql> change master to master_host='192.168.43.141', master_port=3306, master_user='mharep',master_password='Test.123', master_log_file = 'mysql-bin.000001', master_log_pos=1040;

Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;

Query OK, 0 rows affected (0.06 sec)

mysql> show slave status\G;

*************************** 1. row ***************************

              Slave_IO_State: Waiting for master to send event

                  Master_Host: 192.168.43.141

                  Master_User: mharep

                  Master_Port: 3306

                Connect_Retry: 60

              Master_Log_File: mysql-bin.000001

          Read_Master_Log_Pos: 1040

              Relay_Log_File: relay-bin.000002

                Relay_Log_Pos: 320

        Relay_Master_Log_File: mysql-bin.000001

            Slave_IO_Running: Yes

            Slave_SQL_Running: Yes

              Replicate_Do_DB:

          Replicate_Ignore_DB:

          Replicate_Do_Table:

      Replicate_Ignore_Table:

      Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table:

                  Last_Errno: 0

                  Last_Error:

                Skip_Counter: 0

          Exec_Master_Log_Pos: 1040

              Relay_Log_Space: 521

              Until_Condition: None

              Until_Log_File:

                Until_Log_Pos: 0

          Master_SSL_Allowed: No

          Master_SSL_CA_File:

          Master_SSL_CA_Path:

              Master_SSL_Cert:

            Master_SSL_Cipher:

              Master_SSL_Key:

        Seconds_Behind_Master: 0

Master_SSL_Verify_Server_Cert: No

                Last_IO_Errno: 0

                Last_IO_Error:

              Last_SQL_Errno: 0

              Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

            Master_Server_Id: 1

                  Master_UUID: 6882c9b1-e23a-11ea-b7a9-000c29b26880

            Master_Info_File: /var/lib/mysql/master.info

                    SQL_Delay: 0

          SQL_Remaining_Delay: NULL

      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates

          Master_Retry_Count: 86400

                  Master_Bind:

      Last_IO_Error_Timestamp:

    Last_SQL_Error_Timestamp:

              Master_SSL_Crl:

          Master_SSL_Crlpath:

          Retrieved_Gtid_Set:

            Executed_Gtid_Set:

                Auto_Position: 0

        Replicate_Rewrite_DB:

                Channel_Name:

          Master_TLS_Version:

1 row in set (0.00 sec)

MASTER上查看：

mysql> show status like '%rpl_semi_sync%';

+--------------------------------------------+-------+

| Variable_name                              | Value |

+--------------------------------------------+-------+

| Rpl_semi_sync_master_clients              | 2    |

| Rpl_semi_sync_master_net_avg_wait_time    | 0    |

| Rpl_semi_sync_master_net_wait_time        | 0    |

| Rpl_semi_sync_master_net_waits            | 0    |

| Rpl_semi_sync_master_no_times              | 1    |

| Rpl_semi_sync_master_no_tx                | 3    |

| Rpl_semi_sync_master_status                | ON    |

| Rpl_semi_sync_master_timefunc_failures    | 0    |

| Rpl_semi_sync_master_tx_avg_wait_time      | 0    |

| Rpl_semi_sync_master_tx_wait_time          | 0    |

| Rpl_semi_sync_master_tx_waits              | 0    |

| Rpl_semi_sync_master_wait_pos_backtraverse | 0    |

| Rpl_semi_sync_master_wait_sessions        | 0    |

| Rpl_semi_sync_master_yes_tx                | 0    |

| Rpl_semi_sync_slave_status                | OFF  |

+--------------------------------------------+-------+

15 rows in set (0.02 sec)

四、安装MHA

1.安装mha4mysql-node(所有节点)

以下以slave01为示例：

[root@slave01 mha4mysql]# yum install -y perl-DBD-MySQL

[root@slave01 mha4mysql]# pwd

/opt/mha4mysql

[root@slave01 mha4mysql]# ls

mha4mysql-manager-0.56-0.el6.noarch.rpm  mha4mysql-node-0.56-0.el6.noarch.rpm

[root@slave01 mha4mysql]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm

[root@slave01 mha4mysql]# rpm -qa | grep mha

mha4mysql-node-0.56-0.el6.noarch

2.安装mha4mysql-manager(manager节点)

[root@mha-manager opt]# yum install -y perl-DBD-MySQL

[root@mha-manager opt]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm

Preparing...                ########################################### [100%]

  1:mha4mysql-node        ########################################### [100%]

[root@mha-manager opt]# rpm -ivh mha4mysql-manager-0.56-0.el6.noarch.rpm

error: Failed dependencies:

        perl(Log::Dispatch) is needed by mha4mysql-manager-0.56-0.el6.noarch

        perl(Log::Dispatch::File) is needed by mha4mysql-manager-0.56-0.el6.noarch

        perl(Log::Dispatch::Screen) is needed by mha4mysql-manager-0.56-0.el6.noarch

        perl(Parallel::ForkManager) is needed by mha4mysql-manager-0.56-0.el6.noarch

[root@mha-manager opt]# yum install epel-release.noarch -y

[root@mha-manager opt]# yum install -y perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager install perl-Time-HiRes

[root@mha-manager opt]# rpm -ivh mha4mysql-manager-0.56-0.el6.noarch.rpm

Preparing...                ########################################### [100%]

  1:mha4mysql-manager      ########################################### [100%]

[root@mha-manager opt]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm

[root@mha-manager mha4mysql]# rpm -qa | grep mha

mha4mysql-node-0.56-0.el6.noarch

mha4mysql-manager-0.56-0.el6.noarch

3.处理mha4mysql-manager配置文件(manager节点)

[root@mha-manager opt]# mkdir /etc/masterha

[root@mha-manager opt]# mkdir -p /masterha/app1

[root@mha-manager opt]# mkdir /scripts

[root@mha-manager opt]# ls

mha4mysql-manager-0.56-0.el6.noarch.rpm  mha4mysql-manager-0.56.tar.gz  mha4mysql-node-0.56-0.el6.noarch.rpm

[root@mha-manager opt]# tar -xf mha4mysql-manager-0.56.tar.gz

[root@mha-manager opt]# ls

mha4mysql-manager-0.56                  mha4mysql-manager-0.56.tar.gz

mha4mysql-manager-0.56-0.el6.noarch.rpm  mha4mysql-node-0.56-0.el6.noarch.rpm

[root@mha-manager opt]# cd mha4mysql-manager-0.56

[root@mha-manager mha4mysql-manager-0.56]# pwd

/opt/mha4mysql-manager-0.56

[root@mha-manager mha4mysql-manager-0.56]# ls

AUTHORS  bin  COPYING  debian  inc  lib  Makefile.PL  MANIFEST  META.yml  README  rpm  samples  t  tests

[root@mha-manager mha4mysql-manager-0.56]# cp samples/conf/* /etc/masterha/

[root@mha-manager mha4mysql-manager-0.56]# cp samples/scripts/* /scripts/

[root@mha-manager mha4mysql-manager-0.56]# > /etc/masterha/masterha_default.cnf

修改mha-manager配置文件:

[root@mha-manager mha4mysql-manager-0.56]# cat /etc/masterha/app1.cnf

[server default]

manager_workdir=/masterha/app1            #指定工作目录

manager_log=/masterha/app1/manager.log    #指定日志文件

user=manager                              #指定manager管理数据库节点所使用的用户名

password=Test.123                          #对应的是上面用户的密码

ssh_user=root                              #指定配置了ssh免密登录的系统用户

repl_user=mharep                          #指定用于同步数据的用户名

repl_password=Test.123                                  #对应的是上面同步用户的 密码

ping_interval=1                                          #设置监控主库，发送ping包的时间间隔，默认是3秒，尝试三次没有回应时自动进行切换

master_ip_failover_script=/scripts/master_ip_failover    # 该脚本文件请见附录(文末)

secondary_check_script= masterha_secondary_check -s 192.168.43.141 -s 192.168.43.142 -s 192.168.43.143

[server1]

hostname=192.168.43.141

port=3306

master_binlog_dir=/var/lib/mysql    #指定master保存二进制日志的路径，以便MHA可以找到master的日志

candidate_master=1                  #设置为候选master，设置该参数后，发生主从切换以后将会将此库提升为主库

[server2]

hostname=192.168.43.142

port=3306

master_binlog_dir=/var/lib/mysql

candidate_master=1                  #设置为候选master

[server3]

hostname=192.168.43.143

port=3306

master_binlog_dir=/var/lib/mysql

no_master=1                          #设置的不为备选主库

4.启动前测试

（1）验证SSH有效性

[root@mha-manager mha4mysql-manager-0.56]# masterha_check_ssh --conf=/etc/masterha/app1.cnf

Can't locate MHA/SSHCheck.pm in @INC (you may need to install the MHA::SSHCheck module) (@INC contains: /usr/local/perl/lib/site_perl/5.20.3/x86_64-linux /usr/local/perl/lib/site_perl/5.20.3 /usr/local/perl/lib/5.20.3/x86_64-linux /usr/local/perl/lib/5.20.3 .) at /usr/bin/masterha_check_ssh line 25.

BEGIN failed--compilation aborted at /usr/bin/masterha_check_ssh line 25.

[root@mha-manager mha4mysql-manager-0.56]# masterha_check_ssh --conf=/etc/masterha/app1.cnf

Thu Aug 20 05:18:17 2020 - [info] Reading default configuration from /etc/masterha/masterha_default.cnf..

Thu Aug 20 05:18:17 2020 - [info] Reading application default configuration from /etc/masterha/app1.cnf..

Thu Aug 20 05:18:17 2020 - [info] Reading server configuration from /etc/masterha/app1.cnf..

Thu Aug 20 05:18:17 2020 - [info] Starting SSH connection tests..

Thu Aug 20 05:18:18 2020 - [debug]

Thu Aug 20 05:18:17 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.141:22) to [email protected](192.168.43.142:22)..

Thu Aug 20 05:18:17 2020 - [debug]  ok.

Thu Aug 20 05:18:17 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.141:22) to [email protected](192.168.43.143:22)..

Thu Aug 20 05:18:18 2020 - [debug]  ok.

Thu Aug 20 05:18:18 2020 - [debug]

Thu Aug 20 05:18:18 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.142:22) to [email protected](192.168.43.141:22)..

Thu Aug 20 05:18:18 2020 - [debug]  ok.

Thu Aug 20 05:18:18 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.142:22) to [email protected](192.168.43.143:22)..

Thu Aug 20 05:18:18 2020 - [debug]  ok.

Thu Aug 20 05:18:19 2020 - [debug]

Thu Aug 20 05:18:18 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.143:22) to [email protected](192.168.43.141:22)..

Thu Aug 20 05:18:18 2020 - [debug]  ok.

Thu Aug 20 05:18:18 2020 - [debug]  Connecting via SSH from [email protected](192.168.43.143:22) to [email protected](192.168.43.142:22)..

Thu Aug 20 05:18:19 2020 - [debug]  ok.

Thu Aug 20 05:18:19 2020 - [info] All SSH connection tests passed successfully.

[root@mha-manager mha4mysql-manager-0.56]#

（2）验证集群复制的有效性（MySQL必须都启动）

[root@mha-manager mha4mysql-manager-0.56]# masterha_check_repl --conf=/etc/masterha/app1.cnf

Thu Aug 20 15:50:32 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

Thu Aug 20 15:50:32 2020 - [info] Reading application default configuration from /etc/masterha/app1.cnf..

Thu Aug 20 15:50:32 2020 - [info] Reading server configuration from /etc/masterha/app1.cnf..

Thu Aug 20 15:50:32 2020 - [info] MHA::MasterMonitor version 0.56.

Thu Aug 20 15:50:33 2020 - [info] GTID failover mode = 0

Thu Aug 20 15:50:33 2020 - [info] Dead Servers:

Thu Aug 20 15:50:33 2020 - [info] Alive Servers:

Thu Aug 20 15:50:33 2020 - [info]  192.168.43.141(192.168.43.141:3306)

Thu Aug 20 15:50:33 2020 - [info]  192.168.43.142(192.168.43.142:3306)

Thu Aug 20 15:50:33 2020 - [info]  192.168.43.143(192.168.43.143:3306)

Thu Aug 20 15:50:33 2020 - [info] Alive Slaves:

Thu Aug 20 15:50:33 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 15:50:33 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 15:50:33 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 15:50:33 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 15:50:33 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 15:50:33 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 15:50:33 2020 - [info] Current Alive Master: 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 15:50:33 2020 - [info] Checking slave configurations..

Thu Aug 20 15:50:33 2020 - [info]  read_only=1 is not set on slave 192.168.43.142(192.168.43.142:3306).

Thu Aug 20 15:50:33 2020 - [warning]  relay_log_purge=0 is not set on slave 192.168.43.143(192.168.43.143:3306).

Thu Aug 20 15:50:33 2020 - [info] Checking replication filtering settings..

Thu Aug 20 15:50:33 2020 - [info]  binlog_do_db= , binlog_ignore_db=

Thu Aug 20 15:50:33 2020 - [info]  Replication filtering check ok.

Thu Aug 20 15:50:33 2020 - [info] GTID (with auto-pos) is not supported

Thu Aug 20 15:50:33 2020 - [info] Starting SSH connection tests..

Thu Aug 20 15:50:34 2020 - [info] All SSH connection tests passed successfully.

Thu Aug 20 15:50:34 2020 - [info] Checking MHA Node version..

Thu Aug 20 15:50:35 2020 - [info]  Version check ok.

Thu Aug 20 15:50:35 2020 - [info] Checking SSH publickey authentication settings on the current master..

Thu Aug 20 15:50:35 2020 - [info] HealthCheck: SSH to 192.168.43.141 is reachable.

Thu Aug 20 15:50:35 2020 - [info] Master MHA Node version is 0.56.

Thu Aug 20 15:50:35 2020 - [info] Checking recovery script configurations on 192.168.43.141(192.168.43.141:3306)..

Thu Aug 20 15:50:35 2020 - [info]  Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --start_file=mysql-bin.000001

Thu Aug 20 15:50:35 2020 - [info]  Connecting to [email protected](192.168.43.141:22)..

  Creating /var/tmp if not exists..    ok.

  Checking output directory is accessible or not..

  ok.

  Binlog found at /var/lib/mysql, up to mysql-bin.000001

Thu Aug 20 15:50:35 2020 - [info] Binlog setting check done.

Thu Aug 20 15:50:35 2020 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..

Thu Aug 20 15:50:35 2020 - [info]  Executing command : apply_diff_relay_logs --command=test --slave_user='manager' --slave_host=192.168.43.142 --slave_ip=192.168.43.142 --slave_port=3306 --workdir=/var/tmp --target_version=5.7.31-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx

Thu Aug 20 15:50:35 2020 - [info]  Connecting to [email protected](192.168.43.142:22)..

  Checking slave recovery environment settings..

    Opening /var/lib/mysql/relay-log.info ... ok.

    Relay log found at /var/lib/mysql, up to relay-bin.000004

    Temporary relay log file is /var/lib/mysql/relay-bin.000004

    Testing mysql connection and privileges..mysql: [Warning] Using a password on the command line interface can be insecure.

done.

    Testing mysqlbinlog output.. done.

    Cleaning up test file(s).. done.

Thu Aug 20 15:50:35 2020 - [info]  Executing command : apply_diff_relay_logs --command=test --slave_user='manager' --slave_host=192.168.43.143 --slave_ip=192.168.43.143 --slave_port=3306 --workdir=/var/tmp --target_version=5.7.31-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx

Thu Aug 20 15:50:35 2020 - [info]  Connecting to [email protected](192.168.43.143:22)..

  Checking slave recovery environment settings..

    Opening /var/lib/mysql/relay-log.info ... ok.

    Relay log found at /var/lib/mysql, up to relay-bin.000004

    Temporary relay log file is /var/lib/mysql/relay-bin.000004

    Testing mysql connection and privileges..mysql: [Warning] Using a password on the command line interface can be insecure.

done.

    Testing mysqlbinlog output.. done.

    Cleaning up test file(s).. done.

Thu Aug 20 15:50:36 2020 - [info] Slaves settings check done.

Thu Aug 20 15:50:36 2020 - [info]

192.168.43.141(192.168.43.141:3306) (current master)

+--192.168.43.142(192.168.43.142:3306)

+--192.168.43.143(192.168.43.143:3306)

Thu Aug 20 15:50:36 2020 - [info] Checking replication health on 192.168.43.142..

Thu Aug 20 15:50:36 2020 - [info]  ok.

Thu Aug 20 15:50:36 2020 - [info] Checking replication health on 192.168.43.143..

Thu Aug 20 15:50:36 2020 - [info]  ok.

Thu Aug 20 15:50:36 2020 - [warning] master_ip_failover_script is not defined.

Thu Aug 20 15:50:36 2020 - [warning] shutdown_script is not defined.

Thu Aug 20 15:50:36 2020 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

5.启动manager

[root@mha-manager masterha]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &> /var/log/mha_manager.log

五、管理MHA

1.FailOver的配置

MHA管理VIP有两种方案，一种是使用Keepalived，另一种是自己写命令实现增删VIP，由于Keepalived容易受到网络波动造成VIP切换，而且无法在多实例机器上使用，所以建议写脚本管理VIP。

使用脚本管理 VIP 不会自动设置 VIP，所以先手动在 Master 设置 VIP

这里我们先在Master上设置我们的vip:192.168.43.145

ifconfig eth0:1 192.168.43.145 netmask 255.255.255.255

[root@master opt]# ifconfig eth0:1 192.168.43.145 netmask 255.255.255.255

[root@master opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:b2:68:80 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.141/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:feb2:6880/64 scope link

      valid_lft forever preferred_lft forever

[root@master opt]#

2.编写master_ip_failover（见附录）

3.分析现在的拓扑结构以便后续测试的理解：

[root@slave01 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

                  Master_Host: 192.168.43.141

[root@slave02 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

                  Master_Host: 192.168.43.141

[root@slave02 opt]#

可以看出当前的拓扑结构：

Master      -> (192.168.43.141)

Slave      -> (192.168.43.142,192.168.43.143)

vip        -> 192.168.43.145(现在master上，failover后应该漂移到slave01上)

Mha-manager -> 192.168.43.144

4.开始模拟Master切换过程

（1）确保Mha-manager上的监控进程正常运行

[root@mha-manager masterha]# ps -ef | grep perl

root      2514  1604  1 18:32 pts/0    00:00:00 perl /usr/bin/masterha_manager --conf=/etc/masterha/app1.cnf

root      2573  1604  0 18:33 pts/0    00:00:00 grep perl

（2）查看Master上的IP

[root@master opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:b2:68:80 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.141/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:feb2:6880/64 scope link

      valid_lft forever preferred_lft forever

（3）关闭Master上的mysql服务

[root@master opt]# /etc/init.d/mysqld stop

Stopping mysqld:                                          [  OK  ]

[root@master opt]#

（4）观察IP漂移情况

[root@master opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:b2:68:80 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.141/24 brd 192.168.43.255 scope global eth0

    inet6 fe80::20c:29ff:feb2:6880/64 scope link

      valid_lft forever preferred_lft forever

[root@slave01 opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:fb:79:18 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.142/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:fefb:7918/64 scope link

      valid_lft forever preferred_lft forever

可以观察：vip已经漂移到slave01上

（5）观察Master角色的转移

[root@slave01 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

[root@slave01 opt]#

[root@slave02 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

                  Master_Host: 192.168.43.142

可以观察：Master角色迁移到slave01上

（6）分析日志输出（下面为切换的Mha-manager上的整个日志输出）

Thu Aug 20 18:37:14 2020 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)

Thu Aug 20 18:37:14 2020 - [info] Executing secondary network check script: masterha_secondary_check -s 192.168.43.141 -s 192.168.43.142 -s 192.168.43.143  --user=root  --master_host=192.168.43.141  --master_ip=192.168.43.141  --master_port=3306 --master_user=manager --master_password=Test.123 --ping_type=SELECT

Thu Aug 20 18:37:14 2020 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --binlog_prefix=mysql-bin

Thu Aug 20 18:37:14 2020 - [info] HealthCheck: SSH to 192.168.43.141 is reachable.

Monitoring server 192.168.43.141 is reachable, Master is not reachable from 192.168.43.141. OK.

Monitoring server 192.168.43.142 is reachable, Master is not reachable from 192.168.43.142. OK.

Monitoring server 192.168.43.143 is reachable, Master is not reachable from 192.168.43.143. OK.

Thu Aug 20 18:37:14 2020 - [info] Master is not reachable from all other monitoring servers. Failover should start.

Thu Aug 20 18:37:15 2020 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)

Thu Aug 20 18:37:15 2020 - [warning] Connection failed 2 time(s)..

Thu Aug 20 18:37:16 2020 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)

Thu Aug 20 18:37:16 2020 - [warning] Connection failed 3 time(s)..

Thu Aug 20 18:37:17 2020 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)

Thu Aug 20 18:37:17 2020 - [warning] Connection failed 4 time(s)..

Thu Aug 20 18:37:17 2020 - [warning] Master is not reachable from health checker!

Thu Aug 20 18:37:17 2020 - [warning] Master 192.168.43.141(192.168.43.141:3306) is not reachable!

Thu Aug 20 18:37:17 2020 - [warning] SSH is reachable.

Thu Aug 20 18:37:17 2020 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..

Thu Aug 20 18:37:17 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

Thu Aug 20 18:37:17 2020 - [info] Reading application default configuration from /etc/masterha/app1.cnf..

Thu Aug 20 18:37:17 2020 - [info] Reading server configuration from /etc/masterha/app1.cnf..

Thu Aug 20 18:37:18 2020 - [info] GTID failover mode = 0

Thu Aug 20 18:37:18 2020 - [info] Dead Servers:

Thu Aug 20 18:37:18 2020 - [info]  192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:18 2020 - [info] Alive Servers:

Thu Aug 20 18:37:18 2020 - [info]  192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:37:18 2020 - [info]  192.168.43.143(192.168.43.143:3306)

Thu Aug 20 18:37:18 2020 - [info] Alive Slaves:

Thu Aug 20 18:37:18 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:18 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:18 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:37:18 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:18 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:18 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 18:37:18 2020 - [info] Checking slave configurations..

Thu Aug 20 18:37:18 2020 - [info]  read_only=1 is not set on slave 192.168.43.142(192.168.43.142:3306).

Thu Aug 20 18:37:18 2020 - [warning]  relay_log_purge=0 is not set on slave 192.168.43.143(192.168.43.143:3306).

Thu Aug 20 18:37:18 2020 - [info] Checking replication filtering settings..

Thu Aug 20 18:37:18 2020 - [info]  Replication filtering check ok.

Thu Aug 20 18:37:18 2020 - [info] Master is down!

Thu Aug 20 18:37:18 2020 - [info] Terminating monitoring script.

Thu Aug 20 18:37:18 2020 - [info] Got exit code 20 (Master dead).

Thu Aug 20 18:37:18 2020 - [info] MHA::MasterFailover version 0.56.

Thu Aug 20 18:37:18 2020 - [info] Starting master failover.

Thu Aug 20 18:37:18 2020 - [info]

Thu Aug 20 18:37:18 2020 - [info] * Phase 1: Configuration Check Phase..

Thu Aug 20 18:37:18 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] GTID failover mode = 0

Thu Aug 20 18:37:19 2020 - [info] Dead Servers:

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info] Checking master reachability via MySQL(double check)...

Thu Aug 20 18:37:19 2020 - [info]  ok.

Thu Aug 20 18:37:19 2020 - [info] Alive Servers:

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.143(192.168.43.143:3306)

Thu Aug 20 18:37:19 2020 - [info] Alive Slaves:

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 18:37:19 2020 - [info] Starting Non-GTID based failover.

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] ** Phase 1: Configuration Check Phase completed.

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] * Phase 2: Dead Master Shutdown Phase..

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] Forcing shutdown so that applications never connect to the current master..

Thu Aug 20 18:37:19 2020 - [info] Executing master IP deactivation script:

Thu Aug 20 18:37:19 2020 - [info]  /scripts/master_ip_failover --orig_master_host=192.168.43.141 --orig_master_ip=192.168.43.141 --orig_master_port=3306 --command=stopssh --ssh_user=root

VIP Command: start=sudo /sbin/ifconfig eth0:1 192.168.43.145 netmask 255.255.255.255 stop=sudo /sbin/ifconfig eth0:1 down

Disabling the VIP on old master: 192.168.43.141

Thu Aug 20 18:37:19 2020 - [info]  done.

Thu Aug 20 18:37:19 2020 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.

Thu Aug 20 18:37:19 2020 - [info] * Phase 2: Dead Master Shutdown Phase completed.

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] * Phase 3: Master Recovery Phase..

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] * Phase 3.1: Getting Latest Slaves Phase..

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] The latest binary log file/position on all slaves is mysql-bin.000005:154

Thu Aug 20 18:37:19 2020 - [info] Latest slaves (Slaves that received relay log files to the latest):

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 18:37:19 2020 - [info] The oldest binary log file/position on all slaves is mysql-bin.000005:154

Thu Aug 20 18:37:19 2020 - [info] Oldest slaves:

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:37:19 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:19 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:19 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:19 2020 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..

Thu Aug 20 18:37:19 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] Fetching dead master's binary logs..

Thu Aug 20 18:37:20 2020 - [info] Executing command on the dead master 192.168.43.141(192.168.43.141:3306): save_binary_logs --command=save --start_file=mysql-bin.000005  --start_pos=154 --binlog_dir=/var/lib/mysql --output_file=/var/tmp/saved_master_binlog_from_192.168.43.141_3306_20200820183718.binlog --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56

  Creating /var/tmp if not exists..    ok.

Concat binary/relay logs from mysql-bin.000005 pos 154 to mysql-bin.000005 EOF into /var/tmp/saved_master_binlog_from_192.168.43.141_3306_20200820183718.binlog ..

Binlog Checksum enabled

  Dumping binlog format description event, from position 0 to 154.. ok.

  No need to dump effective binlog data from /var/lib/mysql/mysql-bin.000005 (pos starts 154, filesize 154). Skipping.

Binlog Checksum enabled

/var/tmp/saved_master_binlog_from_192.168.43.141_3306_20200820183718.binlog has no effective data events.

Event not exists.

Thu Aug 20 18:37:20 2020 - [info] Additional events were not found from the orig master. No need to save.

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] * Phase 3.3: Determining New Master Phase..

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] Finding the latest slave that has all relay logs for recovering other slaves..

Thu Aug 20 18:37:20 2020 - [info] All slaves received relay logs to the same position. No need to resync each other.

Thu Aug 20 18:37:20 2020 - [info] Searching new master from slaves..

Thu Aug 20 18:37:20 2020 - [info]  Candidate masters from the configuration file:

Thu Aug 20 18:37:20 2020 - [info]  192.168.43.142(192.168.43.142:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:20 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:20 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:37:20 2020 - [info]  Non-candidate masters:

Thu Aug 20 18:37:20 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:37:20 2020 - [info]    Replicating from 192.168.43.141(192.168.43.141:3306)

Thu Aug 20 18:37:20 2020 - [info]    Not candidate for the new Master (no_master is set)

Thu Aug 20 18:37:20 2020 - [info]  Searching from candidate_master slaves which have received the latest relay log events..

Thu Aug 20 18:37:20 2020 - [info] New master is 192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:37:20 2020 - [info] Starting master failover..

Thu Aug 20 18:37:20 2020 - [info]

From:

192.168.43.141(192.168.43.141:3306) (current master)

+--192.168.43.142(192.168.43.142:3306)

+--192.168.43.143(192.168.43.143:3306)

To:

192.168.43.142(192.168.43.142:3306) (new master)

+--192.168.43.143(192.168.43.143:3306)

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] * Phase 3.3: New Master Diff Log Generation Phase..

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] * Phase 3.4: Master Log Apply Phase..

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.

Thu Aug 20 18:37:20 2020 - [info] Starting recovery on 192.168.43.142(192.168.43.142:3306)..

Thu Aug 20 18:37:20 2020 - [info]  This server has all relay logs. Waiting all logs to be applied..

Thu Aug 20 18:37:20 2020 - [info]  done.

Thu Aug 20 18:37:20 2020 - [info]  All relay logs were successfully applied.

Thu Aug 20 18:37:20 2020 - [info] Getting new master's binlog name and position..

Thu Aug 20 18:37:20 2020 - [info]  mysql-bin.000002:154

Thu Aug 20 18:37:20 2020 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.43.142', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='xxx';

Thu Aug 20 18:37:20 2020 - [info] Executing master IP activate script:

Thu Aug 20 18:37:20 2020 - [info]  /scripts/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.43.141 --orig_master_ip=192.168.43.141 --orig_master_port=3306 --new_master_host=192.168.43.142 --new_master_ip=192.168.43.142 --new_master_port=3306 --new_master_user='manager' --new_master_password='Test.123'

VIP Command: start=sudo /sbin/ifconfig eth0:1 192.168.43.145 netmask 255.255.255.255 stop=sudo /sbin/ifconfig eth0:1 down

Set read_only=0 on the new master.

Enabling the VIP - 192.168.43.145 on the new master - 192.168.43.142

Thu Aug 20 18:37:20 2020 - [info]  OK.

Thu Aug 20 18:37:20 2020 - [info] ** Finished master recovery successfully.

Thu Aug 20 18:37:20 2020 - [info] * Phase 3: Master Recovery Phase completed.

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] * Phase 4: Slaves Recovery Phase..

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..

Thu Aug 20 18:37:20 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info] -- Slave diff file generation on host 192.168.43.143(192.168.43.143:3306) started, pid: 2783. Check tmp log /masterha/app1/192.168.43.143_3306_20200820183718.log if it takes time..

Thu Aug 20 18:37:21 2020 - [info]

Thu Aug 20 18:37:21 2020 - [info] Log messages from 192.168.43.143 ...

Thu Aug 20 18:37:21 2020 - [info]

Thu Aug 20 18:37:20 2020 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.

Thu Aug 20 18:37:21 2020 - [info] End of log messages from 192.168.43.143.

Thu Aug 20 18:37:21 2020 - [info] -- 192.168.43.143(192.168.43.143:3306) has the latest relay log events.

Thu Aug 20 18:37:21 2020 - [info] Generating relay diff files from the latest slave succeeded.

Thu Aug 20 18:37:21 2020 - [info]

Thu Aug 20 18:37:21 2020 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..

Thu Aug 20 18:37:21 2020 - [info]

Thu Aug 20 18:37:21 2020 - [info] -- Slave recovery on host 192.168.43.143(192.168.43.143:3306) started, pid: 2785. Check tmp log /masterha/app1/192.168.43.143_3306_20200820183718.log if it takes time..

Thu Aug 20 18:37:22 2020 - [info]

Thu Aug 20 18:37:22 2020 - [info] Log messages from 192.168.43.143 ...

Thu Aug 20 18:37:22 2020 - [info]

Thu Aug 20 18:37:21 2020 - [info] Starting recovery on 192.168.43.143(192.168.43.143:3306)..

Thu Aug 20 18:37:21 2020 - [info]  This server has all relay logs. Waiting all logs to be applied..

Thu Aug 20 18:37:21 2020 - [info]  done.

Thu Aug 20 18:37:21 2020 - [info]  All relay logs were successfully applied.

Thu Aug 20 18:37:21 2020 - [info]  Resetting slave 192.168.43.143(192.168.43.143:3306) and starting replication from the new master 192.168.43.142(192.168.43.142:3306)..

Thu Aug 20 18:37:21 2020 - [info]  Executed CHANGE MASTER.

Thu Aug 20 18:37:21 2020 - [info]  Slave started.

Thu Aug 20 18:37:22 2020 - [info] End of log messages from 192.168.43.143.

Thu Aug 20 18:37:22 2020 - [info] -- Slave recovery on host 192.168.43.143(192.168.43.143:3306) succeeded.

Thu Aug 20 18:37:22 2020 - [info] All new slave servers recovered successfully.

Thu Aug 20 18:37:22 2020 - [info]

Thu Aug 20 18:37:22 2020 - [info] * Phase 5: New master cleanup phase..

Thu Aug 20 18:37:22 2020 - [info]

Thu Aug 20 18:37:22 2020 - [info] Resetting slave info on the new master..

Thu Aug 20 18:37:22 2020 - [info]  192.168.43.142: Resetting slave info succeeded.

Thu Aug 20 18:37:22 2020 - [info] Master failover to 192.168.43.142(192.168.43.142:3306) completed successfully.

Thu Aug 20 18:37:22 2020 - [info]

----- Failover Report -----

app1: MySQL Master failover 192.168.43.141(192.168.43.141:3306) to 192.168.43.142(192.168.43.142:3306) succeeded

Master 192.168.43.141(192.168.43.141:3306) is down!

Check MHA Manager logs at mha-manager:/masterha/app1/manager.log for details.

Started automated(non-interactive) failover.

Invalidated master IP address on 192.168.43.141(192.168.43.141:3306)

The latest slave 192.168.43.142(192.168.43.142:3306) has all relay logs for recovery.

Selected 192.168.43.142(192.168.43.142:3306) as a new master.

192.168.43.142(192.168.43.142:3306): OK: Applying all logs succeeded.

192.168.43.142(192.168.43.142:3306): OK: Activated master IP address.

192.168.43.143(192.168.43.143:3306): This host has the latest relay log events.

Generating relay diff files from the latest slave succeeded.

192.168.43.143(192.168.43.143:3306): OK: Applying all logs succeeded. Slave started, replicating from 192.168.43.142(192.168.43.142:3306)

192.168.43.142(192.168.43.142:3306): Resetting slave info succeeded.

Master failover to 192.168.43.142(192.168.43.142:3306) completed successfully.

（7）观察manager上的perl开启的监控进程是否存在？

[root@mha-manager ~]# ps -ef | grep perl

root      2813  2796  0 18:41 pts/0    00:00:00 grep perl

观察可知：MHA在切换完成后会结束 Manager 进程

5.还原操作

（1）删除锁文件

MHA每次故障切换后都会生成一个app1.failover.complete这样的文件，如果不加这个参数，需要删除这个文件才能再次启动

[root@mha-manager masterha]# rm -rf  /masterha/app1/app1.failover.complete

或者启动时添加（--ignore_last_failover 忽略上次切换）：

nohup masterha_manager --conf=/etc/masterha/app1.cnf &> /var/log/mha_manager.log --ignore_last_failover &

（2）原MASTER上从新指定slave01为新的master角色服务器

[root@slave01 opt]# mysql -uroot -p'Test.123' -e 'show master status\G;'

mysql: [Warning] Using a password on the command line interface can be insecure.

*************************** 1. row ***************************

            File: mysql-bin.000002

        Position: 154

    Binlog_Do_DB:

Binlog_Ignore_DB:

Executed_Gtid_Set:

[root@slave01 opt]#

[root@master opt]# /etc/init.d/mysqld start

Starting mysqld:                                          [  OK  ]

[root@master opt]# mysql -uroot -p'Test.123'

mysql: [Warning] Using a password on the command line interface can be insecure.

Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 3

Server version: 5.7.31-log MySQL Community Server (GPL)

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

由于演示，这里就不锁库了：

mysql> change master to master_host='192.168.43.142', master_port=3306, master_user='mharep',master_password='Test.123', master_log_file = 'mysql-bin.000002', master_log_pos=154;

Query OK, 0 rows affected, 2 warnings (0.04 sec)

mysql> start slave;

Query OK, 0 rows affected (0.01 sec)

mysql> show slave status\G;

*************************** 1. row ***************************

              Slave_IO_State: Waiting for master to send event

                  Master_Host: 192.168.43.142

                  Master_User: mharep

                  Master_Port: 3306

                Connect_Retry: 60

              Master_Log_File: mysql-bin.000002

          Read_Master_Log_Pos: 154

              Relay_Log_File: relay-bin.000002

                Relay_Log_Pos: 320

        Relay_Master_Log_File: mysql-bin.000002

            Slave_IO_Running: Yes

            Slave_SQL_Running: Yes

              Replicate_Do_DB:

          Replicate_Ignore_DB:

          Replicate_Do_Table:

      Replicate_Ignore_Table:

      Replicate_Wild_Do_Table:

  Replicate_Wild_Ignore_Table:

                  Last_Errno: 0

                  Last_Error:

                Skip_Counter: 0

          Exec_Master_Log_Pos: 154

              Relay_Log_Space: 521

              Until_Condition: None

              Until_Log_File:

                Until_Log_Pos: 0

          Master_SSL_Allowed: No

          Master_SSL_CA_File:

          Master_SSL_CA_Path:

              Master_SSL_Cert:

            Master_SSL_Cipher:

              Master_SSL_Key:

        Seconds_Behind_Master: 0

Master_SSL_Verify_Server_Cert: No

                Last_IO_Errno: 0

                Last_IO_Error:

              Last_SQL_Errno: 0

              Last_SQL_Error:

  Replicate_Ignore_Server_Ids:

            Master_Server_Id: 2

                  Master_UUID: 0b529b47-e2b6-11ea-9d4e-000c29fb7918

            Master_Info_File: /var/lib/mysql/master.info

                    SQL_Delay: 0

          SQL_Remaining_Delay: NULL

      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates

          Master_Retry_Count: 86400

                  Master_Bind:

      Last_IO_Error_Timestamp:

    Last_SQL_Error_Timestamp:

              Master_SSL_Crl:

          Master_SSL_Crlpath:

          Retrieved_Gtid_Set:

            Executed_Gtid_Set:

                Auto_Position: 0

        Replicate_Rewrite_DB:

                Channel_Name:

          Master_TLS_Version:

1 row in set (0.00 sec)

（3）切换MASTER角色（manager上操作）这时不要开启manager进程，即不开启:nohup masterha_manager --conf=/etc/masterha/app1.cnf &> /var/log/mha_manager.log &

[root@mha-manager ~]# ps -ef | grep perl

root      2936  2796  0 18:51 pts/0    00:00:00 grep perl

[root@mha-manager ~]#

[root@mha-manager ~]#

[root@mha-manager ~]# masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.43.141 --new_master_port=3306 --orig_master_is_new_slave

# 填写: yes

Thu Aug 20 18:51:17 2020 - [info] MHA::MasterRotate version 0.56.

Thu Aug 20 18:51:17 2020 - [info] Starting online master switch..

Thu Aug 20 18:51:17 2020 - [info]

Thu Aug 20 18:51:17 2020 - [info] * Phase 1: Configuration Check Phase..

Thu Aug 20 18:51:17 2020 - [info]

Thu Aug 20 18:51:17 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.

Thu Aug 20 18:51:17 2020 - [info] Reading application default configuration from /etc/masterha/app1.cnf..

Thu Aug 20 18:51:17 2020 - [info] Reading server configuration from /etc/masterha/app1.cnf..

Thu Aug 20 18:51:18 2020 - [info] GTID failover mode = 0

Thu Aug 20 18:51:18 2020 - [info] Current Alive Master: 192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:51:18 2020 - [info] Alive Slaves:

Thu Aug 20 18:51:18 2020 - [info]  192.168.43.141(192.168.43.141:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:51:18 2020 - [info]    Replicating from 192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:51:18 2020 - [info]    Primary candidate for the new Master (candidate_master is set)

Thu Aug 20 18:51:18 2020 - [info]  192.168.43.143(192.168.43.143:3306)  Version=5.7.31-log (oldest major version between slaves) log-bin:enabled

Thu Aug 20 18:51:18 2020 - [info]    Replicating from 192.168.43.142(192.168.43.142:3306)

Thu Aug 20 18:51:18 2020 - [info]    Not candidate for the new Master (no_master is set)

It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.43.142(192.168.43.142:3306)? (YES/no): yes

Thu Aug 20 18:51:21 2020 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..

Thu Aug 20 18:51:21 2020 - [info]  ok.

Thu Aug 20 18:51:21 2020 - [info] Checking MHA is not monitoring or doing failover..

Thu Aug 20 18:51:21 2020 - [info] Checking replication health on 192.168.43.141..

Thu Aug 20 18:51:21 2020 - [info]  ok.

Thu Aug 20 18:51:21 2020 - [info] Checking replication health on 192.168.43.143..

Thu Aug 20 18:51:21 2020 - [info]  ok.

Thu Aug 20 18:51:21 2020 - [info] 192.168.43.141 can be new master.

Thu Aug 20 18:51:21 2020 - [info]

From:

192.168.43.142(192.168.43.142:3306) (current master)

+--192.168.43.141(192.168.43.141:3306)

+--192.168.43.143(192.168.43.143:3306)

To:

192.168.43.141(192.168.43.141:3306) (new master)

+--192.168.43.143(192.168.43.143:3306)

+--192.168.43.142(192.168.43.142:3306)

Starting master switch from 192.168.43.142(192.168.43.142:3306) to 192.168.43.141(192.168.43.141:3306)? (yes/NO): yes

Thu Aug 20 18:51:24 2020 - [info] Checking whether 192.168.43.141(192.168.43.141:3306) is ok for the new master..

Thu Aug 20 18:51:24 2020 - [info]  ok.

Thu Aug 20 18:51:24 2020 - [info] 192.168.43.142(192.168.43.142:3306): SHOW SLAVE STATUS returned empty result. To check replication filtering rules, temporarily executing CHANGE MASTER to a dummy host.

Thu Aug 20 18:51:24 2020 - [info] 192.168.43.142(192.168.43.142:3306): Resetting slave pointing to the dummy host.

Thu Aug 20 18:51:24 2020 - [info] ** Phase 1: Configuration Check Phase completed.

Thu Aug 20 18:51:24 2020 - [info]

Thu Aug 20 18:51:24 2020 - [info] * Phase 2: Rejecting updates Phase..

Thu Aug 20 18:51:24 2020 - [info]

master_ip_online_change_script is not defined. If you do not disable writes on the current master manually, applications keep writing on the current master. Is it ok to proceed? (yes/NO): yes

Thu Aug 20 18:51:27 2020 - [info] Locking all tables on the orig master to reject updates from everybody (including root):

Thu Aug 20 18:51:27 2020 - [info] Executing FLUSH TABLES WITH READ LOCK..

Thu Aug 20 18:51:27 2020 - [info]  ok.

Thu Aug 20 18:51:27 2020 - [info] Orig master binlog:pos is mysql-bin.000002:154.

Thu Aug 20 18:51:27 2020 - [info]  Waiting to execute all relay logs on 192.168.43.141(192.168.43.141:3306)..

Thu Aug 20 18:51:27 2020 - [info]  master_pos_wait(mysql-bin.000002:154) completed on 192.168.43.141(192.168.43.141:3306). Executed 0 events.

Thu Aug 20 18:51:27 2020 - [info]  done.

Thu Aug 20 18:51:27 2020 - [info] Getting new master's binlog name and position..

Thu Aug 20 18:51:27 2020 - [info]  mysql-bin.000006:154

Thu Aug 20 18:51:27 2020 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.43.141', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000006', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='xxx';

Thu Aug 20 18:51:27 2020 - [info]

Thu Aug 20 18:51:27 2020 - [info] * Switching slaves in parallel..

Thu Aug 20 18:51:27 2020 - [info]

Thu Aug 20 18:51:27 2020 - [info] -- Slave switch on host 192.168.43.143(192.168.43.143:3306) started, pid: 2941

Thu Aug 20 18:51:27 2020 - [info]

Thu Aug 20 18:51:28 2020 - [info] Log messages from 192.168.43.143 ...

Thu Aug 20 18:51:28 2020 - [info]

Thu Aug 20 18:51:27 2020 - [info]  Waiting to execute all relay logs on 192.168.43.143(192.168.43.143:3306)..

Thu Aug 20 18:51:27 2020 - [info]  master_pos_wait(mysql-bin.000002:154) completed on 192.168.43.143(192.168.43.143:3306). Executed 0 events.

Thu Aug 20 18:51:27 2020 - [info]  done.

Thu Aug 20 18:51:27 2020 - [info]  Resetting slave 192.168.43.143(192.168.43.143:3306) and starting replication from the new master 192.168.43.141(192.168.43.141:3306)..

Thu Aug 20 18:51:27 2020 - [info]  Executed CHANGE MASTER.

Thu Aug 20 18:51:27 2020 - [info]  Slave started.

Thu Aug 20 18:51:28 2020 - [info] End of log messages from 192.168.43.143 ...

Thu Aug 20 18:51:28 2020 - [info]

Thu Aug 20 18:51:28 2020 - [info] -- Slave switch on host 192.168.43.143(192.168.43.143:3306) succeeded.

Thu Aug 20 18:51:28 2020 - [info] Unlocking all tables on the orig master:

Thu Aug 20 18:51:28 2020 - [info] Executing UNLOCK TABLES..

Thu Aug 20 18:51:28 2020 - [info]  ok.

Thu Aug 20 18:51:28 2020 - [info] Starting orig master as a new slave..

Thu Aug 20 18:51:28 2020 - [info]  Resetting slave 192.168.43.142(192.168.43.142:3306) and starting replication from the new master 192.168.43.141(192.168.43.141:3306)..

Thu Aug 20 18:51:28 2020 - [info]  Executed CHANGE MASTER.

Thu Aug 20 18:51:28 2020 - [info]  Slave started.

Thu Aug 20 18:51:28 2020 - [info] All new slave servers switched successfully.

Thu Aug 20 18:51:28 2020 - [info]

Thu Aug 20 18:51:28 2020 - [info] * Phase 5: New master cleanup phase..

Thu Aug 20 18:51:28 2020 - [info]

Thu Aug 20 18:51:28 2020 - [info]  192.168.43.141: Resetting slave info succeeded.

Thu Aug 20 18:51:28 2020 - [info] Switching master to 192.168.43.141(192.168.43.141:3306) completed successfully.

[root@mha-manager ~]#

（4）分析转移情况

[root@slave02 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

                  Master_Host: 192.168.43.141


[root@slave01 opt]# mysql -uroot -p'Test.123' -e 'show slave status\G'  | grep Master_Host

mysql: [Warning] Using a password on the command line interface can be insecure.

                  Master_Host: 192.168.43.141

[root@slave01 opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:fb:79:18 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.142/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:fefb:7918/64 scope link

      valid_lft forever preferred_lft forever

结论是：数据库主从转移成功，但vip没有迁移

（5）手动修复vip问题

[root@slave01 opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:fb:79:18 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.142/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:fefb:7918/64 scope link

      valid_lft forever preferred_lft forever

[root@slave01 opt]# ip addr delete 192.168.43.145/32 dev eth0:1

[root@slave01 opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:fb:79:18 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.142/24 brd 192.168.43.255 scope global eth0

    inet6 fe80::20c:29ff:fefb:7918/64 scope link

      valid_lft forever preferred_lft forever

[root@master opt]# ifconfig eth0:1 192.168.43.145 netmask 255.255.255.255

[root@master opt]# ip a

1: lo: mtu 65536 qdisc noqueue state UNKNOWN

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

    inet6 ::1/128 scope host

      valid_lft forever preferred_lft forever

2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 00:0c:29:b2:68:80 brd ff:ff:ff:ff:ff:ff

    inet 192.168.43.141/24 brd 192.168.43.255 scope global eth0

    inet 192.168.43.145/32 brd 192.168.43.145 scope global eth0:1

    inet6 fe80::20c:29ff:feb2:6880/64 scope link

      valid_lft forever preferred_lft forever

五、总结

优点：

开源，用Perl编写。

方案成熟，故障切换时，MHA会做日志补齐操作，尽可能减少数据丢失，保证数据一。

部署不需要改变现有架构。

限制：

各个节点要打通SSH信任，有一定的安全隐患。

没有Slave的高可用。

自带的脚本不足，例如虚IP配置需要自己写命令或者依赖其他软件。

需要手动清理中继日志。

总的来说，MHA是一套非常优秀而且使用比较广的高可用程序，它可以自动补齐日志使得一致性有保证，部署的时候不需要改变原有架构就可以使用。

但是使用起来还是有一点复杂的，因为MHA不接管VIP，所以要自己写脚本实现，而且只保证Master高可用，没有Slave高可用，还有就是中继日志要自己设定时任务来清理。

不管怎么说，在没有更好的方案下，MHA还是值得使用的。

参阅：

https://blog.51cto.com/14154700/2472806

https://github.com/yoshinorim/mha4mysql-manager/wiki/Installation#installing-mha-node

https://segmentfault.com/a/1190000017486693

附：master_ip_failover文件内容（vip为192.168.43.145）

[root@mha-manager masterha]# cat /scripts/master_ip_failover

#!/usr/bin/env perl

use strict;

use warnings FATAL => 'all';

use Getopt::Long;

use MHA::DBHelper;

my (

  $command,        $ssh_user,        $orig_master_host,

  $orig_master_ip, $orig_master_port, $new_master_host,

  $new_master_ip,  $new_master_port,  $new_master_user,

  $new_master_password

);

my $vip = '192.168.43.145';

my $key = '1';

my $ssh_start_vip = "sudo /sbin/ifconfig eth0:$key $vip netmask 255.255.255.255";

my $ssh_stop_vip = "sudo /sbin/ifconfig eth0:$key down";

GetOptions(

  'command=s'            => \$command,

  'ssh_user=s'            => \$ssh_user,

  'orig_master_host=s'    => \$orig_master_host,

  'orig_master_ip=s'      => \$orig_master_ip,

  'orig_master_port=i'    => \$orig_master_port,

  'new_master_host=s'    => \$new_master_host,

  'new_master_ip=s'      => \$new_master_ip,

  'new_master_port=i'    => \$new_master_port,

  'new_master_user=s'    => \$new_master_user,

  'new_master_password=s' => \$new_master_password,

);

exit &main();

sub main {

  print "\n\n VIP Command: start=$ssh_start_vip stop=$ssh_stop_vip\n\n";

  if ( $command eq "stop" || $command eq "stopssh" ) {

    # $orig_master_host, $orig_master_ip, $orig_master_port are passed.

    # If you manage master ip address at global catalog database,

    # invalidate orig_master_ip here.

    my $exit_code = 1;

    eval {

      print "Disabling the VIP on old master: $orig_master_host \n";

      &stop_vip();

      # updating global catalog, etc

      $exit_code = 0;

    };

    if ($@) {

      warn "Got Error: $@\n";

      exit $exit_code;

    }

    exit $exit_code;

  }

  elsif ( $command eq "start" ) {

    # all arguments are passed.

    # If you manage master ip address at global catalog database,

    # activate new_master_ip here.

    # You can also grant write access (create user, set read_only=0, etc) here.

    my $exit_code = 10;

    eval {

      my $new_master_handler = new MHA::DBHelper();

      # args: hostname, port, user, password, raise_error_or_not

      $new_master_handler->connect( $new_master_ip, $new_master_port,

        $new_master_user, $new_master_password, 1 );

      ## Set read_only=0 on the new master

      $new_master_handler->disable_log_bin_local();

      print "Set read_only=0 on the new master.\n";

      $new_master_handler->disable_read_only();

      $new_master_handler->disconnect();

      print "Enabling the VIP - $vip on the new master - $new_master_host \n";

      &start_vip();

      $exit_code = 0;

    };

    if ($@) {

      warn $@;

      # If you want to continue failover, exit 10.

      exit $exit_code;

    }

    exit $exit_code;

  }

  elsif ( $command eq "status" ) {

    print "Check script.. OK \n";

    # do nothing

    exit 0;

  }

  else {

    &usage();

    exit 1;

  }

}

sub start_vip() {

    `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;

}

sub stop_vip() {

    return 0  unless  ($ssh_user);

    `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;

}

sub usage {

  print

"Usage: master_ip_failover --command=start|stop|stopssh|status --orig_master_host=host --orig_master_ip=ip --orig_master_port=port --new_master_host=host --new_master_ip=ip --new_master_port=port\n";

}

[root@mha-manager masterha]#

你可能感兴趣的:(MySQL半同步 + MHA架构配置文档)

  • 【iOS】MVC设计模式 Magnetic_h iosmvc设计模式objective-c学习ui
    MVC前言如何设计一个程序的结构，这是一门专门的学问，叫做"架构模式"（architecturalpattern），属于编程的方法论。MVC模式就是架构模式的一种。它是Apple官方推荐的App开发架构，也是一般开发者最先遇到、最经典的架构。MVC各层controller层Controller/ViewController/VC（控制器）负责协调Model和View，处理大部分逻辑它将数据从Mod
  • 微服务下功能权限与数据权限的设计与实现 nbsaas-boot 微服务java架构
    在微服务架构下，系统的功能权限和数据权限控制显得尤为重要。随着系统规模的扩大和微服务数量的增加，如何保证不同用户和服务之间的访问权限准确、细粒度地控制，成为设计安全策略的关键。本文将讨论如何在微服务体系中设计和实现功能权限与数据权限控制。1.功能权限与数据权限的定义功能权限：指用户或系统角色对特定功能的访问权限。通常是某个用户角色能否执行某个操作，比如查看订单、创建订单、修改用户资料等。数据权限：
  • mysql禁用远程登录 igotyback mysql
    去mysql库中的user表里，将host都改成localhost之后刷新权限FLUSHPRIVILEGES;
  • 腾讯云技术深度探索：构建高效云原生微服务架构 我的运维人生 云原生架构腾讯云运维开发技术共享
    腾讯云技术深度探索：构建高效云原生微服务架构在当今快速发展的技术环境中，云原生技术已成为企业数字化转型的关键驱动力。腾讯云作为行业领先的云服务提供商，不断推出创新的产品和技术，助力企业构建高效、可扩展的云原生微服务架构。本文将深入探讨腾讯云在微服务领域的最新进展，并通过一个实际案例展示如何在腾讯云平台上构建云原生应用。腾讯云微服务架构概览腾讯云微服务架构基于云原生理念，旨在帮助企业快速实现应用的容
  • 关于提高复杂业务逻辑代码可读性的思考 编程经验分享 开发经验java数据库开发语言
    目录前言需求场景常规写法拆分方法领域对象总结前言实际工作中大部分时间都是在写业务逻辑，一般都是三层架构，表示层（Controller）接收客户端请求，并对入参做检验，业务逻辑层（Service）负责处理业务逻辑，一般开发都是在这一层中写具体的业务逻辑。数据访问层（Dao）是直接和数据库交互的，用于查数据给业务逻辑层，或者是将业务逻辑层处理后的数据写入数据库。简单的增删改查接口不用多说，基本上写好一
  • MYSQL面试系列-04 king01299 面试mysql面试
    MYSQL面试系列-0417.关于redolog和binlog的刷盘机制、redolog、undolog作用、GTID是做什么的？innodb_flush_log_at_trx_commit及sync_binlog参数意义双117.1innodb_flush_log_at_trx_commit该变量定义了InnoDB在每次事务提交时，如何处理未刷入（flush）的重做日志信息（redolog）。它
  • 18、架构-可观测性之聚合度量 大树~~ 架构javapython后端架构
    聚合度量聚合度量是指对系统运行时产生的各种指标数据进行收集、聚合和分析，以了解系统的健康状况和性能表现。聚合度量是可观测性的关键组成部分，通过对度量数据的分析，可以及时发现系统中的异常和瓶颈。以下是对聚合度量各个方面的详细解析，并结合具体的数据案例和技术支撑。指标收集收集系统运行时产生的各种指标数据是聚合度量的基础。常见的指标包括CPU使用率、内存使用率、请求处理时间、请求数、错误率等。以下是指标
  • 关于Mysql 中 Row size too large (＞ 8126) 错误的解决和理解 秋刀prince mysqlmysql数据库
    提示：啰嗦一嘴，数据库的任何操作和验证前，一定要记得先备份！！！不会有错；文章目录问题发现一、问题导致的可能原因1、页大小2、行格式2.1compact格式2.2Redundant格式2.3Dynamic格式2.4Compressed格式3、BLOB和TEXT列二、解决办法1、修改页大小（不推荐）2、修改行格式3、修改数据类型为BLOB和TEXT列4、其他优化方式（可以参考使用）4.1合理设置数据
  • BART&BERT Ambition_LAO 深度学习
    BART和BERT都是基于Transformer架构的预训练语言模型。模型架构：BERT(BidirectionalEncoderRepresentationsfromTransformers)主要是一个编码器（Encoder）模型，它使用了Transformer的编码器部分来处理输入的文本，并生成文本的表示。BERT特别擅长理解语言的上下文，因为它在预训练阶段使用了掩码语言模型（MLM）任务，即
  • 系统架构设计师 需求分析篇二 AmHardy 软件架构设计师系统架构需求分析面向对象分析分析模型UML和SysML
    面向对象分析方法1.用例模型构建用例模型一般需要经历4个阶段：识别参与者：识别与系统交互的所有事物。合并需求获得用例：将需求分配给予其相关的参与者。细化用例描述：详细描述每个用例的功能。调整用例模型：优化用例之间的关系和结构，前三个阶段是必需的。2.用例图的三元素参与者：使用系统的用户或其他外部系统和设备。用例：系统所提供的服务。通信关联：参与者和用例之间的关系，或用例与用例之间的关系。3.识别参
  • Java爬虫框架（一）--架构设计 狼图腾-狼之传说 java框架java任务html解析器存储电子商务
    一、架构图那里搜网络爬虫框架主要针对电子商务网站进行数据爬取，分析，存储，索引。爬虫：爬虫负责爬取，解析，处理电子商务网站的网页的内容数据库：存储商品信息索引：商品的全文搜索索引Task队列：需要爬取的网页列表Visited表：已经爬取过的网页列表爬虫监控平台：web平台可以启动，停止爬虫，管理爬虫，task队列，visited表。二、爬虫1.流程1)Scheduler启动爬虫器，TaskMast
  • Armv8.3 体系结构扩展--原文版 代码改变世界ctw ARM-TEE-Androidarmv8嵌入式arm架构安全架构芯片TrustzoneSecureboot
    快速链接:.ARMv8/ARMv9架构入门到精通-[目录]付费专栏-付费课程【购买须知】:个人博客笔记导读目录(全部)TheArmv8.3architectureextensionTheArmv8.3architectureextensionisanextensiontoArmv8.2.Itaddsmandatoryandoptionalarchitecturalfeatures.Somefeat
  • MongoDB知识概括 GeorgeLin98 持久层mongodb
    MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
  • 【ARM Cortex-M 系列 2.3 -- Cortex-M7 Debug event 详细介绍】 主公讲 ARM #ARM系列arm开发debugevent
    请阅读【嵌入式开发学习必备专栏】文章目录Cortex-M7DebugeventDebugeventsCortex-M7Debugevent在ARMCortex-M7架构中，调试事件（DebugEvent）是由于调试原因而触发的事件。一个调试事件会导致以下几种情况之一发生：进入调试状态：如果启用了停滞调试（HaltingDebug），一个调试事件会使处理器在调试状态下停滞。通过将DHCSR.C_DE
  • 基于STM32与Qt的自动平衡机器人：从控制到人机交互的的详细设计流程 极客小张 stm32qt机器人物联网人机交互毕业设计c语言
    一、项目概述目标和用途本项目旨在开发一款基于STM32控制的自动平衡机器人，结合步进电机和陀螺仪传感器，实现对平衡机器人的精确控制。该机器人可以用于教育、科研、娱乐等多个领域，帮助用户了解自动控制、机器人运动学等相关知识。技术栈关键词STM32单片机步进电机陀螺仪传感器AD采集电路Qt人机界面实时数据监控二、系统架构系统架构设计本项目的系统架构设计包括以下主要组件：控制单元:STM32单片机传感器
  • JAVA·一个简单的登录窗口 MortalTom java开发语言学习
    文章目录概要整体架构流程技术名词解释技术细节资源概要JavaSwing是Java基础类库的一部分，主要用于开发图形用户界面（GUI）程序整体架构流程新建项目，导入sql.jar包（链接放在了文末），编译项目并运行技术名词解释一、特点丰富的组件提供了多种可视化组件，如按钮（JButton）、文本框（JTextField）、标签（JLabel）、下拉列表（JComboBox）等，可以满足不同的界面设计
  • 入门MySQL——查询语法练习 K_un
    前言：前面几篇文章为大家介绍了DML以及DDL语句的使用方法，本篇文章将主要讲述常用的查询语法。其实MySQL官网给出了多个示例数据库供大家实用查询，下面我们以最常用的员工示例数据库为准，详细介绍各自常用的查询语法。1.员工示例数据库导入官方文档员工示例数据库介绍及下载链接：https://dev.mysql.com/doc/employee/en/employees-installation.h
  • ARMV8体系结构简介：概述 简单同学 ARMV8体系结构ARMV8
    1.前言本文主要概括的介绍ARMV8体系结构定义了哪些内容，概括的说：ARM体系结构定义了PE的行为，不会定义具体的实现ARM体系结构也定义了debug体系结构和trace体系结构ARM体系结构采用RISC指令集（1）长度一致的寄存器；（2）load/store架构，数据处理操作只能对寄存器内容进行处理，不会直接对内存的内容进行处理；（3）简单寻址方式，load/store地址来源于寄存器或指令域
  • 博客网站制作教程 2401_85194651 javamaven
    首先就是技术框架：后端：Java+SpringBoot数据库：MySQL前端：Vue.js数据库连接：JPA(JavaPersistenceAPI)1.项目结构blog-app/├──backend/│├──src/main/java/com/example/blogapp/││├──BlogApplication.java││├──config/│││└──DatabaseConfig.java
  • Table列表复现框实现【勾选-搜索-再勾选】 ～四时春～ java开发语言elementuivue
    Table列表复现框实现【勾选-搜索-再勾选】概要整体架构流程代码实现技术细节注意参考文献概要最近在开发时遇到一个问题，在进行表单渲染时，正常选中没有问题，单如果需要搜索选中时，一个是已选中的不会回填，二是在搜索的结果中进行选中，没有实现，经过排查，查找资料后实现。例如：整体架构流程具体的实现效果如下：代码实现{{scope.row.userName}}已选区{{userItem.userName
  • ubuntu安装wordpress lissettecarlr
    1安装nginx网上安装方式很多，这就就直接用apt-get了apt-getinstallnginx不用启动啥，然后直接在浏览器里面输入IP:80就能看到nginx的主页了。如果修改了一些配置可以使用下列命令重启一下systemctlrestartnginx.service2安装mysql输入安装前也可以更新一下软件源，在安装过程中将会让你输入数据库的密码。sudoapt-getinstallmy
  • 深入浅出 -- 系统架构之负载均衡Nginx的性能优化 xiaoli8748_软件开发 系统架构系统架构负载均衡nginx
    一、Nginx性能优化到这里文章的篇幅较长了，最后再来聊一下关于Nginx的性能优化，主要就简单说说收益最高的几个优化项，在这块就不再展开叙述了，毕竟影响性能都有多方面原因导致的，比如网络、服务器硬件、操作系统、后端服务、程序自身、数据库服务等，对于性能调优比较感兴趣的可以参考之前《JVM性能调优》中的调优思想。优化一：打开长连接配置通常Nginx作为代理服务，负责分发客户端的请求，那么建议开启H
  • 计算机毕业设计PHP仓储综合管理系统（源码+程序+VUE+lw+部署） java毕设程序源码王哥 php课程设计vue.js
    该项目含有源码、文档、程序、数据库、配套开发软件、软件安装教程。欢迎交流项目运行环境配置：phpStudy+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue+Express。项目技术：原生PHP++Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是小皮phpstudy最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
  • AI大模型的架构演进与最新发展 季风泯灭的季节 AI大模型应用技术二人工智能架构
    随着深度学习的发展，AI大模型（LargeLanguageModels,LLMs）在自然语言处理、计算机视觉等领域取得了革命性的进展。本文将详细探讨AI大模型的架构演进，包括从Transformer的提出到GPT、BERT、T5等模型的历史演变，并探讨这些模型的技术细节及其在现代人工智能中的核心作用。一、基础模型介绍：Transformer的核心原理Transformer架构的背景在Transfo
  • 信息系统安全相关概念(上) YuanDaima2048 课程笔记基础概念安全信息安全笔记
    文章总览：YuanDaiMa2048博客文章总览下篇:信息系统安全相关概念(下)信息系统安全相关概念[上]信息系统概述信息系统信息系统架构信息系统发展趋势：信息系统日趋大型化、复杂化信息系统面临的安全威胁信息系统安全架构设计--以云计算为例信息系统安全需求及安全策略自主访问控制策略DAC强制访问控制策略MAC信息系统概述信息系统用于收集、存储和处理数据以及传递信息、知识和数字产品的一组集成组件。几
  • You have an error in your SQL syntax； check the manual that corresponds to your MySQL server version 努力的菜鸟~ sql数据库
    YouhaveanerrorinyourSQLsyntax;checkthemanualthatcorrespondstoyourMySQLserverversionfortherightsyntaxtousenear‘IDENTIFIEDBY‘123456’WITHGRANTOPTION’atline1在mysql5.7之前GRANTALLPRIVILEGESON*.*TO'root'@'%'I
  • 程序员架构师主要是做什么_程序员架构师：职责、技能与挑战 绿色小猪
    免费备考资料（2024年11月软考）：历年试题+视频课合集+电子讲义点击领取>>>免费刷题：2024年11月软考备考刷题点此进入>>>程序员架构师的角色定位在软件开发领域，程序员架构师是一个至关重要的角色。他们不仅需要深入理解业务需求，还要将其转化为技术上的解决方案。程序员架构师是项目中的技术领航者，负责制定和维护软件系统的整体架构，确保系统的可扩展性、可维护性和性能。他们的工作涉及从概念化到实现
  • mysql学习教程，从入门到精通，TOP 和MySQL LIMIT 子句（15） 知识分享小能手 大数据数据库MySQLmysql学习oracle数据库开发语言adb大数据
    1、TOP和MySQLLIMIT子句内容在SQL中，不同的数据库系统对于限制查询结果的数量有不同的实现方式。TOP关键字主要用于SQLServer和Access数据库中，而LIMIT子句则主要用于MySQL、PostgreSQL（通过LIMIT/OFFSET语法）、SQLite等数据库中。下面将分别详细介绍这两个功能的语法、语句以及案例。1.1、TOP子句（SQLServer和Access）1.1
  • metaRTC8.0，一个全新架构的webRTC SDK库 metaRTC webrtc音视频
    概述metaRTC8.0是metaRTC开源以来架构变化最大的一个版本，是metaIPC3.0等高性能的基础。metaRTC8.0是一个全新架构版本，并非在metaRTC7.0版本上简单升级，在QOS/语音对讲/内存占用/视频文件录制读取等方面新增多个模块，在弱网对抗/语音对讲/内存优化等效果上有显著提升。metaRTC8.0在一年多的开发中进行了近200次迭代，metaRTC8.0社区版计划在2
  • 鲲鹏 ARM 架构 麒麟 Lylin v10 安装 Nginx (离线) 焚木灵 arm开发架构nginx服务器
    最近做一个银行的项目，银行的服务器是鲲鹏ARM架构的服务器，并且是麒麟v10的系统，这里记录一下在无法访问外网安装Nginx的方法。其他文章：鲲鹏ARM架构麒麟Lylinv10安装Mysql8.3(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Node和NVM(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Pm2(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装P
  • PHP，安卓，UI，java，linux视频教程合集 cocos2d-x小菜 javaUIlinuxPHPandroid
    ╔-----------------------------------╗┆                           
  • zookeeper admin 笔记 braveCS zookeeper
      Required Software 1) JDK>=1.6 2)推荐使用ensemble的ZooKeeper(至少3台)，并run on separate machines 3)在Yahoo!，zk配置在特定的RHEL boxes里，2个cpu，2G内存，80G硬盘   数据和日志目录 1)数据目录里的文件是zk节点的持久化备份，包括快照和事务日
  • Spring配置多个连接池 easterfly spring
    项目中需要同时连接多个数据库的时候，如何才能在需要用到哪个数据库就连接哪个数据库呢？ Spring中有关于dataSource的配置：     <bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource"   &nb
  • Mysql 171815164 mysql
    例如，你想myuser使用mypassword从任何主机连接到mysql服务器的话。 GRANT ALL PRIVILEGES ON *.* TO 'myuser'@'%'IDENTIFIED BY 'mypassword' WI TH GRANT OPTION; 如果你想允许用户myuser从ip为192.168.1.6的主机连接到mysql服务器，并使用mypassword作
  • CommonDAO（公共/基础DAO） g21121 DAO
            好久没有更新博客了，最近一段时间工作比较忙，所以请见谅，无论你是爱看呢还是爱看呢还是爱看呢，总之或许对你有些帮助。         DAO(Data Access Object)是一个数据访问（顾名思义就是与数据库打交道）接口，DAO一般在业
  • 直言有讳 永夜-极光 感悟随笔
      1.转载地址:http://blog.csdn.net/jasonblog/article/details/10813313   精华: “直言有讳”是阿里巴巴提倡的一种观念，而我在此之前并没有很深刻的认识。为什么呢？就好比是读书时候做阅读理解，我喜欢我自己的解读，并不喜欢老师给的意思。在这里也是。我自己坚持的原则是互相尊重，我觉得阿里巴巴很多价值观其实是基本的做人
  • 安装CentOS 7 和Win 7后，Win7 引导丢失 随便小屋 centos
    一般安装双系统的顺序是先装Win7，然后在安装CentOS，这样CentOS可以引导WIN 7启动。但安装CentOS7后，却找不到Win7 的引导，稍微修改一点东西即可。 一、首先具有root 的权限。      即进入Terminal后输入命令su，然后输入密码即可 二、利用vim编辑器打开/boot/grub2/grub.cfg文件进行修改 v
  • Oracle备份与恢复案例 aijuans oracle
    Oracle备份与恢复案例 一. 理解什么是数据库恢复当我们使用一个数据库时，总希望数据库的内容是可靠的、正确的，但由于计算机系统的故障（硬件故障、软件故障、网络故障、进程故障和系统故障）影响数据库系统的操作，影响数据库中数据的正确性，甚至破坏数据库，使数据库中全部或部分数据丢失。因此当发生上述故障后，希望能重构这个完整的数据库，该处理称为数据库恢复。恢复过程大致可以分为复原(Restore)与
  • JavaEE开源快速开发平台G4Studio v5.0发布 無為子
      我非常高兴地宣布,今天我们最新的JavaEE开源快速开发平台G4Studio_V5.0版本已经正式发布。   访问G4Studio网站 http://www.g4it.org   2013-04-06 发布G4Studio_V5.0版本 功能新增 (1). 新增了调用Oracle存储过程返回游标，并将游标映射为Java List集合对象的标
  • Oracle显示根据高考分数模拟录取 百合不是茶 PL/SQL编程oracle例子模拟高考录取学习交流
    题目要求: 1,创建student表和result表 2,pl/sql对学生的成绩数据进行处理 3,处理的逻辑是根据每门专业课的最低分线和总分的最低分数线自动的将录取和落选     1,创建student表,和result表 学生信息表; create table student( student_id number primary key,--学生id
  • 优秀的领导与差劲的领导 bijian1013 领导管理团队
    责任 优秀的领导：优秀的领导总是对他所负责的项目担负起责任。如果项目不幸失败了，那么他知道该受责备的人是他自己，并且敢于承认错误。 差劲的领导：差劲的领导觉得这不是他的问题，因此他会想方设法证明是他的团队不行，或是将责任归咎于团队中他不喜欢的那几个成员身上。 努力工作 优秀的领导：团队领导应该是团队成员的榜样。至少，他应该与团队中的其他成员一样努力工作。这仅仅因为他
  • js函数在浏览器下的兼容 Bill_chen jquery浏览器IEDWRext
      做前端开发的工程师，少不了要用FF进行测试，纯js函数在不同浏览器下，名称也可能不同。对于IE6和FF，取得下一结点的函数就不尽相同：   IE6：node.nextSibling,对于FF是不能识别的；   FF：node.nextElementSibling,对于IE是不能识别的； 兼容解决方式：var Div = node.nextSibl
  • 【JVM四】老年代垃圾回收：吞吐量垃圾收集器(Throughput GC) bit1129 垃圾回收
    吞吐量与用户线程暂停时间   衡量垃圾回收算法优劣的指标有两个： 吞吐量越高，则算法越好 暂停时间越短，则算法越好 首先说明吞吐量和暂停时间的含义。   垃圾回收时，JVM会启动几个特定的GC线程来完成垃圾回收的任务，这些GC线程与应用的用户线程产生竞争关系，共同竞争处理器资源以及CPU的执行时间。GC线程不会对用户带来的任何价值，因此，好的GC应该占
  • J2EE监听器和过滤器基础 白糖_ J2EE
    Servlet程序由Servlet，Filter和Listener组成，其中监听器用来监听Servlet容器上下文。 监听器通常分三类：基于Servlet上下文的ServletContex监听，基于会话的HttpSession监听和基于请求的ServletRequest监听。   ServletContex监听器 ServletContex又叫application
  • 博弈AngularJS讲义(16) - 提供者 boyitech jsAngularJSapiAngularProvider
      Angular框架提供了强大的依赖注入机制，这一切都是有注入器(injector)完成. 注入器会自动实例化服务组件和符合Angular API规则的特殊对象，例如控制器，指令，过滤器动画等。   那注入器怎么知道如何去创建这些特殊的对象呢？ Angular提供了5种方式让注入器创建对象，其中最基础的方式就是提供者(provider), 其余四种方式(Value, Fac
  • java-写一函数f(a,b)，它带有两个字符串参数并返回一串字符，该字符串只包含在两个串中都有的并按照在a中的顺序。 bylijinnan java
    public class CommonSubSequence { /** * 题目：写一函数f(a,b)，它带有两个字符串参数并返回一串字符，该字符串只包含在两个串中都有的并按照在a中的顺序。 * 写一个版本算法复杂度O(N^2)和一个O(N) 。 * * O(N^2)：对于a中的每个字符，遍历b中的每个字符，如果相同，则拷贝到新字符串中。 * O(
  • sqlserver 2000 无法验证产品密钥 Chen.H sqlwindowsSQL ServerMicrosoft
    在 Service Pack 4 (SP 4), 是运行 Microsoft Windows Server 2003、 Microsoft Windows Storage Server 2003 或 Microsoft Windows 2000 服务器上您尝试安装 Microsoft SQL Server 2000 通过卷许可协议 (VLA) 媒体。 这样做, 收到以下错误信息CD KEY的 SQ
  • [新概念武器]气象战争 comsci
           气象战争的发动者必须是拥有发射深空航天器能力的国家或者组织....        原因如下:        地球上的气候变化和大气层中的云层涡旋场有密切的关系,而维持一个在大气层某个层次
  • oracle 中 rollup、cube、grouping 使用详解 daizj oraclegroupingrollupcube
    oracle 中 rollup、cube、grouping 使用详解 -- 使用oracle 样例表演示 转自namesliu -- 使用oracle 的样列库，演示 rollup, cube, grouping 的用法与使用场景    --- ROLLUP ， 为了理解分组的成员数量，我增加了 分组的计数  COUNT(SAL)   
  • 技术资料汇总分享 Dead_knight 技术资料汇总 分享
    本人汇总的技术资料，分享出来，希望对大家有用。 http://pan.baidu.com/s/1jGr56uE 资料主要包含： Workflow->工作流相关理论、框架(OSWorkflow、JBPM、Activiti、fireflow...) Security->java安全相关资料(SSL、SSO、SpringSecurity、Shiro、JAAS...) Ser
  • 初一下学期难记忆单词背诵第一课 dcj3sjt126com englishword
    could 能够 minute 分钟 Tuesday 星期二 February 二月 eighteenth 第十八 listen 听 careful 小心的，仔细的 short 短的 heavy 重的 empty 空的 certainly 当然 carry 携带；搬运 tape 磁带 basket 蓝子 bottle 瓶 juice 汁，果汁 head 头；头部
  • 截取视图的图片, 然后分享出去 dcj3sjt126com OSObjective-C
    OS 7 has a new method that allows you to draw a view hierarchy into the current graphics context. This can be used to get an UIImage very fast. I implemented a category method on UIView to get the vi
  • MySql重置密码 fanxiaolong MySql重置密码
    方法一:  在my.ini的[mysqld]字段加入： skip-grant-tables 重启mysql服务，这时的mysql不需要密码即可登录数据库  然后进入mysql mysql>use mysql;  mysql>更新 user set password=password('新密码') WHERE User='root'; mysq
  • Ehcache（03）——Ehcache中储存缓存的方式 234390216 ehcacheMemoryStoreDiskStore存储驱除策略
    Ehcache中储存缓存的方式   目录 1     堆内存（MemoryStore） 1.1     指定可用内存 1.2     驱除策略 1.3     元素过期 2   &nbs
  • spring mvc中的@propertysource jackyrong spring mvc
      在spring mvc中，在配置文件中的东西，可以在java代码中通过注解进行读取了： @PropertySource  在spring 3.1中开始引入 比如有配置文件 config.properties mongodb.url=1.2.3.4 mongodb.db=hello 则代码中   @PropertySource(&
  • 重学单例模式 lanqiu17 单例Singleton模式
    最近在重新学习设计模式，感觉对模式理解更加深刻。觉得有必要记下来。 第一个学的就是单例模式，单例模式估计是最好理解的模式了。它的作用就是防止外部创建实例，保证只有一个实例。 单例模式的常用实现方式有两种，就人们熟知的饱汉式与饥汉式，具体就不多说了。这里说下其他的实现方式 静态内部类方式: package test.pattern.singleton.statics; publ
  • .NET开源核心运行时，且行且珍惜 netcome java.net开源
    背景 2014年11月12日，ASP.NET之父、微软云计算与企业级产品工程部执行副总裁Scott Guthrie，在Connect全球开发者在线会议上宣布，微软将开源全部.NET核心运行时，并将.NET 扩展为可在 Linux 和 Mac OS 平台上运行。.NET核心运行时将基于MIT开源许可协议发布，其中将包括执行.NET代码所需的一切项目——CLR、JIT编译器、垃圾收集器（GC）和核心
  • 使用oscahe缓存技术减少与数据库的频繁交互 Everyday都不同 Web高并发oscahe缓存
    此前一直不知道缓存的具体实现，只知道是把数据存储在内存中，以便下次直接从内存中读取。对于缓存的使用也没有概念，觉得缓存技术是一个比较”神秘陌生“的领域。但最近要用到缓存技术，发现还是很有必要一探究竟的。   缓存技术使用背景：一般来说，对于web项目，如果我们要什么数据直接jdbc查库好了，但是在遇到高并发的情形下，不可能每一次都是去查数据库，因为这样在高并发的情形下显得不太合理——
  • Spring+Mybatis 手动控制事务 toknowme mybatis
    @Override    public boolean testDelete(String jobCode) throws Exception {       boolean flag = false;  &nbs
  • 菜鸟级的android程序员面试时候需要掌握的知识点 xp9802 android
    熟悉Android开发架构和API调用 掌握APP适应不同型号手机屏幕开发技巧 熟悉Android下的数据存储  熟练Android Debug Bridge Tool 熟练Eclipse/ADT及相关工具  熟悉Android框架原理及Activity生命周期 熟练进行Android UI布局 熟练使用SQLite数据库； 熟悉Android下网络通信机制，S
按字母分类： ABCDEFGHIJKLMNOPQRSTUVWXYZ其他