AlrinNi

MySQL5.7 MHA测试with GTID

我的实验MHA

环境准备：

192.168.199.101 manager
192.168.199.102 node01
192.168.199.103 node02
192.168.199.104 node03

主机环境

[root@manager ~]# uname -a
Linux manager 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

###步骤1，准备MySQL5.7
#本文预先安装了MySQL5.7到/opt/mysql7

cd /data/
mkdir MHANODE01
mkdir {data,log,tmp}
useradd mysql
echo "111111" | passwd mysql --stdin
chown -R mysql:mysql /data/MHANODE01/
#初始化数据库，初始化密码需要到日志里找
/opt/mysql7/bin/mysqld --initialize --user=mysql --basedir=/opt/mysql7 --datadir=/data/MHANODE01/data --explicit_defaults_for_timestamp
#建立my.cnf，核心参数：
[client]
default-character-set = utf8
port = 3306
socket = /data/MHANODE01/mysql.sock

[mysqld]
server-id = 1
collation-server = utf8_unicode_ci
init-connect = 'SET NAMES utf8'
character-set-server = utf8
port        = 3306
socket        = /data/MHANODE01/mysql.sock
datadir = /data/MHANODE01/data
log-error = /data/MHANODE01/mysql.err
pid-file = /data/MHANODE01/mysql.pid

gtid_mode=on
#auto-increment-increment = 2
#auto-increment-offset = 2
sync_binlog = 1
sync_master_info = 1
sync_relay_log = 1
sync_relay_log_info = 1
enforce-gtid-consistency=on
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 1M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log-bin = /data/MHANODE01/data/mysql-bin
relay_log = /data/MHANODE01/data/relay-bin
##cascaded replication for slave to write binlog.
log_slave_updates = 1
#read-only=1
binlog_format = row
slow_query_log = 1
slow_query_log_file = /data/MHANODE01/log/slowquery.log
long_query_time = 1
general_log = off
general_log_file = /data/MHANODE01/log/general.log
#skip-grant-tables
#rpl_semi_sync_slave_enabled = 1

[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout

#建立错误日志文件

touch /data/MHANODE02/mysql.err
chown mysql:mysql /data/MHANODE02/mysql.err
#启动数据库
/opt/mysql7/bin/mysqld_safe --defaults-file='/data/MHANODE01/my.cnf' --user=mysql &

#首次登陆数据库，并更改密码：

/opt/mysql7/bin/mysql -uroot -p -S '/data/MHANODE01/mysql.sock'

#登陆后更改密码,并登出，重新登入

set password=password('111111');
flush privileges;
exit
/opt/mysql7/bin/mysql -uroot -p -S '/data/MHANODE01/mysql.sock'

###以上第一步建立数据库，另外两个节点同样设置，只是需要注意server-id必须不同，可以设置2，3...
###需要放开3306端口的tcp和udp访问，或者直接关闭防火墙：

systemctl stop firewalld
systemctl disable firewalld

###设置好3台独立数据库后，设置一主多从的复制：
#主库上：

grant replication slave, replication client on *.* to replica@'192.168.199.%';

mysqldump -uroot -p111111 -S /data/MHANODE01/mysql.sock --single-transaction --master-data=2 --opt -A > /tmp/fullnode01.sql

scp /tmp/fullnode01.sql node02:/tmp/
scp /tmp/fullnode01.sql node03:/tmp/

#从库上：

mysql -uroot -p111111 -S /data/MHANODE02/mysql.sock < /tmp/fullnode01.sql
##登录MySQL

reset master;
 change  master to master_host='192.168.199.102',master_port=3306,master_user='replica',master_password='111111',master_auto_position=1;
 start slave;

#检查slave状态

show salve status\G

#对于一主多从的复制，详细情况请参阅其他主题

###安装MHA的过程
#所有节点，包含manager节点，都需要安装mha4mysql-node包

[root@localhost ~]# mkdir /usr/local/src/mha4mysql-node
[root@localhost ~]# cd /usr/local/src/mha4mysql-node
[root@localhost mha4mysql-node]# wget https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.58/mha4mysql-node-0.58.tar.gz

cpan Module::Install
perl -MCPAN -e "install Class::Load"
yum install -y perl-Mail-Sender perl-Email-Date-Format perl-MIME-Types perl-MIME-Lite perl-Parallel-ForkManager perl-Mail-Sendmail 
yum install -y perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-YAML-Tiny perl-PAR-Dist perl-Module-ScanDeps perl-Module-CoreList perl-Module-Build perl-CPAN perl-YAML perl-CPANPLUS perl-File-Remove perl-Module-Install
yum install -y perl-DBD-MySQL perl-DBI mysql-libs

yum -y install cpanm
cpanm Module::Runtime

tar -zxvf mha4mysql-node-0.58.tar.gz
cd mha4mysql-node-0.58
perl Makefile.PL 
make && make install

#manager 节点上安装mha4mysql-manager-0.58

mkdir /usr/local/src/mha4mysql-manager
cd /usr/local/src/mha4mysql-manager
wget https://github.com/yoshinorim/mha4mysql-manager/releases/download/v0.58/mha4mysql-manager-0.58.tar.gz
tar -zxvf mha4mysql-manager-0.58.tar.gz 
cd mha4mysql-manager-0.58
perl Makefile.PL 
make && make install

#如果安装都没出错，则可以配置管理节点文件

mkdir /etc/masterha
 cd /etc/masterha/
 vim app1.cnf

[server default]
manager_workdir=/etc/masterha
manager_log=/etc/masterha/manager.log
#mysql用户和密码
password=111111
user=mha
#监控主库，发送ping包的时间间隔，默认是3秒，尝试3次不成功，则自动进行切换操作
ping_interval=3
#复制用户
repl_password=111111
repl_user=replica
#report_script=/usr/local/send_report
#通过第三方机器确认目标主库是否存活,不是必须的,就算没有也是能用
secondary_check_script=masterha_secondary_check -s 192.168.199.101 
#故障自动切换VIP调用脚本,不是必须的,就算没有也是能用,
master_ip_failover_script=/etc/masterha/scripts/master_ip_failover

#ssh用户
ssh_user=root
ssh_port=22
[server1]
hostname=192.168.199.102
candidate_master=1
[server2]
hostname=192.168.199.103
candidate_master=1 

[server3] 
hostname=192.168.199.104
candidate_master=1

#vip脚本文件

#!/usr/bin/env perl
use strict;
use warnings FATAL =>'all';

use Getopt::Long;

my (
$command,          $ssh_user,        $orig_master_host, $orig_master_ip,
$orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
);

my $vip = '192.168.199.105/24';  # Virtual IP
my $key = "1";
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down";
my $exit_code = 0;

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,
);

exit &main();

[root@manager scripts]# 
[root@manager scripts]# 
[root@manager scripts]# cat master_ip_failover
#!/usr/bin/env perl
use strict;
use warnings FATAL =>'all';

use Getopt::Long;

my (
$command,          $ssh_user,        $orig_master_host, $orig_master_ip,
$orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
);

my $vip = '192.168.199.105/24';  # Virtual IP
my $key = "1";
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down";
my $exit_code = 0;

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,
);

exit &main();

sub main {

#print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_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 "\n\n\n***************************************************************\n";
            print "Disabling the VIP - $vip on old master: $orig_master_host\n";
            print "***************************************************************\n\n\n\n";
&stop_vip();
            $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 {
            print "\n\n\n***************************************************************\n";
            print "Enabling the VIP - $vip on new master: $new_master_host \n";
            print "***************************************************************\n\n\n\n";
&start_vip();
            $exit_code = 0;
        };
        if ($@) {
            warn $@;
            exit $exit_code;
        }
        exit $exit_code;
}
elsif ( $command eq "status" ) {
        print "Checking the Status of the script.. OK \n";
        `ssh $orig_master_host \" $ssh_start_vip \"`;
        exit 0;
}
else {
&usage();
        exit 1;
}
}

# A simple system call that enable the VIP on the new master
sub start_vip() {
`ssh $new_master_host " $ssh_start_vip "`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`ssh $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=po
rt –new_master_host=host –new_master_ip=ip –new_master_port=port\n";
}

#测试脚本文件：
#启动

./master_ip_failover --command=start  --new_master_host=192.168.199.105

#停止

./master_ip_failover --command=stop --orig_master_host=192.168.199.102

#检查状态

./master_ip_failover --command=status --orig_master_host=192.168.199.102

###测试
#启动

masterha_manager --conf=/etc/masterha/app1.cnf &

#查看日志

tail -f /etc/masterha/manager.log

#停止

masterha_stop --conf=/etc/masterha/app1.cnf

###测试fail-over
#启动

masterha_manager --conf=/etc/masterha/app1.cnf &

#master上杀死MYSQL进程

killall mysqld

#日志过程

Sun Aug 16 19:34:10 2020 - [info] Checking master_ip_failover_script status:
Sun Aug 16 19:34:10 2020 - [info]   /etc/masterha/scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.199.102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 
Checking the Status of the script.. OK 
Sun Aug 16 19:34:10 2020 - [info]  OK.
Sun Aug 16 19:34:10 2020 - [warning] shutdown_script is not defined.
Sun Aug 16 19:34:10 2020 - [info] Set master ping interval 3 seconds.
Sun Aug 16 19:34:10 2020 - [info] Set secondary check script: masterha_secondary_check -s 192.168.199.101
Sun Aug 16 19:34:10 2020 - [info] Starting ping health check on 192.168.199.102(192.168.199.102:3306)..
Sun Aug 16 19:34:22 2020 - [warning] Got error when monitoring master:  at /usr/local/share/perl5/MHA/MasterMonitor.pm line 489.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln491] Target master's advisory lock is already held by someone. Please check whether you monitor the same master from multiple monitoring processes.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln511] Error happened on health checking.  at /usr/local/bin/masterha_manager line 50.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Sun Aug 16 19:34:22 2020 - [info] Got exit code 1 (Not master dead).
Sun Aug 16 19:35:10 2020 - [info] MHA::MasterFailover version 0.58.
Sun Aug 16 19:35:10 2020 - [info] Starting master failover.
Sun Aug 16 19:35:10 2020 - [info] 
Sun Aug 16 19:35:10 2020 - [info] * Phase 1: Configuration Check Phase..
Sun Aug 16 19:35:10 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] GTID failover mode = 1
Sun Aug 16 19:35:12 2020 - [info] Dead Servers:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info] Checking master reachability via MySQL(double check)...
Sun Aug 16 19:35:12 2020 - [info]  ok.
Sun Aug 16 19:35:12 2020 - [info] Alive Servers:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)
Sun Aug 16 19:35:12 2020 - [info] Alive Slaves:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] Starting GTID based failover.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] ** Phase 1: Configuration Check Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 2: Dead Master Shutdown Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] Forcing shutdown so that applications never connect to the current master..
Sun Aug 16 19:35:12 2020 - [info] Executing master IP deactivation script:
Sun Aug 16 19:35:12 2020 - [info]   /etc/masterha/scripts/master_ip_failover --orig_master_host=192.168.199.102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 --command=stopssh --ssh_user=root  

***************************************************************
Disabling the VIP - 192.168.199.105/24 on old master: 192.168.199.102
***************************************************************

Sun Aug 16 19:35:12 2020 - [info]  done.
Sun Aug 16 19:35:12 2020 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Sun Aug 16 19:35:12 2020 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3: Master Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] The latest binary log file/position on all slaves is mysql-bin.000002:3766
Sun Aug 16 19:35:12 2020 - [info] Retrieved Gtid Set: e30e52c8-df91-11ea-8231-0050563df028:9-14
Sun Aug 16 19:35:12 2020 - [info] Latest slaves (Slaves that received relay log files to the latest):
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] The oldest binary log file/position on all slaves is mysql-bin.000002:3766
Sun Aug 16 19:35:12 2020 - [info] Retrieved Gtid Set: e30e52c8-df91-11ea-8231-0050563df028:9-14
Sun Aug 16 19:35:12 2020 - [info] Oldest slaves:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.3: Determining New Master Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] Searching new master from slaves..
Sun Aug 16 19:35:12 2020 - [info]  Candidate masters from the configuration file:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]  Non-candidate masters:
Sun Aug 16 19:35:12 2020 - [info]  Searching from candidate_master slaves which have received the latest relay log events..
Sun Aug 16 19:35:12 2020 - [info] New master is 192.168.199.103(192.168.199.103:3306)
Sun Aug 16 19:35:12 2020 - [info] Starting master failover..
Sun Aug 16 19:35:12 2020 - [info] 
From:
192.168.199.102(192.168.199.102:3306) (current master)
 +--192.168.199.103(192.168.199.103:3306)
 +--192.168.199.104(192.168.199.104:3306)

To:
192.168.199.103(192.168.199.103:3306) (new master)
 +--192.168.199.104(192.168.199.104:3306)
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.3: New Master Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info]  Waiting all logs to be applied.. 
Sun Aug 16 19:35:12 2020 - [info]   done.
Sun Aug 16 19:35:12 2020 - [info] Getting new master's binlog name and position..
Sun Aug 16 19:35:12 2020 - [info]  mysql-bin.000001:1341
Sun Aug 16 19:35:12 2020 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.199.103', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='replica', MASTER_PASSWORD='xxx';
Sun Aug 16 19:35:12 2020 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: mysql-bin.000001, 1341, e30e52c8-df91-11ea-8231-0050563df028:1-14
Sun Aug 16 19:35:12 2020 - [info] Executing master IP activate script:
Sun Aug 16 19:35:12 2020 - [info]   /etc/masterha/scripts/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.199.102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 --new_master_host=192.168.199.103 --new_master_ip=192.168.199.103 --new_master_port=3306 --new_master_user='mha'   --new_master_password=xxx
Unknown option: new_master_user
Unknown option: new_master_password

***************************************************************
Enabling the VIP - 192.168.199.105/24 on new master: 192.168.199.103 
***************************************************************

Sun Aug 16 19:35:12 2020 - [info]  OK.
Sun Aug 16 19:35:12 2020 - [info] ** Finished master recovery successfully.
Sun Aug 16 19:35:12 2020 - [info] * Phase 3: Master Recovery Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 4: Slaves Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 4.1: Starting Slaves in parallel..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] -- Slave recovery on host 192.168.199.104(192.168.199.104:3306) started, pid: 11958. Check tmp log /etc/masterha/192.168.199.104_3306_20200816193510.log if it takes time..
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] Log messages from 192.168.199.104 ...
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info]  Resetting slave 192.168.199.104(192.168.199.104:3306) and starting replication from the new master 192.168.199.103(192.168.199.103:3306)..
Sun Aug 16 19:35:12 2020 - [info]  Executed CHANGE MASTER.
Sun Aug 16 19:35:13 2020 - [info]  Slave started.
Sun Aug 16 19:35:13 2020 - [info]  gtid_wait(e30e52c8-df91-11ea-8231-0050563df028:1-14) completed on 192.168.199.104(192.168.199.104:3306). Executed 0 events.
Sun Aug 16 19:35:14 2020 - [info] End of log messages from 192.168.199.104.
Sun Aug 16 19:35:14 2020 - [info] -- Slave on host 192.168.199.104(192.168.199.104:3306) started.
Sun Aug 16 19:35:14 2020 - [info] All new slave servers recovered successfully.
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] * Phase 5: New master cleanup phase..
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] Resetting slave info on the new master..
Sun Aug 16 19:35:14 2020 - [info]  192.168.199.103: Resetting slave info succeeded.
Sun Aug 16 19:35:14 2020 - [info] Master failover to 192.168.199.103(192.168.199.103:3306) completed successfully.
Sun Aug 16 19:35:14 2020 - [info] 

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

app1: MySQL Master failover 192.168.199.102(192.168.199.102:3306) to 192.168.199.103(192.168.199.103:3306) succeeded

Master 192.168.199.102(192.168.199.102:3306) is down!

Check MHA Manager logs at manager:/etc/masterha/manager.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.199.102(192.168.199.102:3306)
Selected 192.168.199.103(192.168.199.103:3306) as a new master.
192.168.199.103(192.168.199.103:3306): OK: Applying all logs succeeded.
192.168.199.103(192.168.199.103:3306): OK: Activated master IP address.
192.168.199.104(192.168.199.104:3306): OK: Slave started, replicating from 192.168.199.103(192.168.199.103:3306)
192.168.199.103(192.168.199.103:3306): Resetting slave info succeeded.
Master failover to 192.168.199.103(192.168.199.103:3306) completed successfully.
^C
[root@manager masterha]# tail -f /etc/masterha/manager.log ^C
[root@manager masterha]# more /etc/masterha/manager.log
Sun Aug 16 19:34:08 2020 - [info] MHA::MasterMonitor version 0.58.
Sun Aug 16 19:34:09 2020 - [info] GTID failover mode = 1
Sun Aug 16 19:34:09 2020 - [info] Dead Servers:
Sun Aug 16 19:34:09 2020 - [info] Alive Servers:
Sun Aug 16 19:34:09 2020 - [info]   192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:34:09 2020 - [info]   192.168.199.103(192.168.199.103:3306)
Sun Aug 16 19:34:09 2020 - [info]   192.168.199.104(192.168.199.104:3306)
Sun Aug 16 19:34:09 2020 - [info] Alive Slaves:
Sun Aug 16 19:34:09 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:34:09 2020 - [info]     GTID ON
Sun Aug 16 19:34:09 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:34:09 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:34:09 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:34:09 2020 - [info]     GTID ON
Sun Aug 16 19:34:09 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:34:09 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:34:09 2020 - [info] Current Alive Master: 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:34:09 2020 - [info] Checking slave configurations..
Sun Aug 16 19:34:09 2020 - [info]  read_only=1 is not set on slave 192.168.199.103(192.168.199.103:3306).
Sun Aug 16 19:34:09 2020 - [info]  read_only=1 is not set on slave 192.168.199.104(192.168.199.104:3306).
Sun Aug 16 19:34:09 2020 - [info] Checking replication filtering settings..
Sun Aug 16 19:34:09 2020 - [info]  binlog_do_db= , binlog_ignore_db= 
Sun Aug 16 19:34:09 2020 - [info]  Replication filtering check ok.
Sun Aug 16 19:34:09 2020 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package check
ing.
Sun Aug 16 19:34:09 2020 - [info] Checking SSH publickey authentication settings on the current master..
Sun Aug 16 19:34:10 2020 - [info] HealthCheck: SSH to 192.168.199.102 is reachable.
Sun Aug 16 19:34:10 2020 - [info] 
192.168.199.102(192.168.199.102:3306) (current master)
 +--192.168.199.103(192.168.199.103:3306)
 +--192.168.199.104(192.168.199.104:3306)

Sun Aug 16 19:34:10 2020 - [info] Checking master_ip_failover_script status:
Sun Aug 16 19:34:10 2020 - [info]   /etc/masterha/scripts/master_ip_failover --command=status --ssh_user=roo
t --orig_master_host=192.168.199.102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 
Checking the Status of the script.. OK 
Sun Aug 16 19:34:10 2020 - [info]  OK.
Sun Aug 16 19:34:10 2020 - [warning] shutdown_script is not defined.
Sun Aug 16 19:34:10 2020 - [info] Set master ping interval 3 seconds.
Sun Aug 16 19:34:10 2020 - [info] Set secondary check script: masterha_secondary_check -s 192.168.199.101
Sun Aug 16 19:34:10 2020 - [info] Starting ping health check on 192.168.199.102(192.168.199.102:3306)..
Sun Aug 16 19:34:22 2020 - [warning] Got error when monitoring master:  at /usr/local/share/perl5/MHA/Master
Monitor.pm line 489.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln491] Target master's advis
ory lock is already held by someone. Please check whether you monitor the same master from multiple monitori
ng processes.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln511] Error happened on hea
lth checking.  at /usr/local/bin/masterha_manager line 50.
Sun Aug 16 19:34:22 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on mon
itoring servers.
Sun Aug 16 19:34:22 2020 - [info] Got exit code 1 (Not master dead).
Sun Aug 16 19:35:10 2020 - [info] MHA::MasterFailover version 0.58.
Sun Aug 16 19:35:10 2020 - [info] Starting master failover.
Sun Aug 16 19:35:10 2020 - [info] 
Sun Aug 16 19:35:10 2020 - [info] * Phase 1: Configuration Check Phase..
Sun Aug 16 19:35:10 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] GTID failover mode = 1
Sun Aug 16 19:35:12 2020 - [info] Dead Servers:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info] Checking master reachability via MySQL(double check)...
Sun Aug 16 19:35:12 2020 - [info]  ok.
Sun Aug 16 19:35:12 2020 - [info] Alive Servers:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)
Sun Aug 16 19:35:12 2020 - [info] Alive Slaves:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] Starting GTID based failover.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] ** Phase 1: Configuration Check Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 2: Dead Master Shutdown Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] Forcing shutdown so that applications never connect to the current master.
.
Sun Aug 16 19:35:12 2020 - [info] Executing master IP deactivation script:
Sun Aug 16 19:35:12 2020 - [info]   /etc/masterha/scripts/master_ip_failover --orig_master_host=192.168.199.
102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 --command=stopssh --ssh_user=root  

***************************************************************
Disabling the VIP - 192.168.199.105/24 on old master: 192.168.199.102
***************************************************************

Sun Aug 16 19:35:12 2020 - [info]  done.
Sun Aug 16 19:35:12 2020 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead
 master.
Sun Aug 16 19:35:12 2020 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3: Master Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] The latest binary log file/position on all slaves is mysql-bin.000002:3766
Sun Aug 16 19:35:12 2020 - [info] Retrieved Gtid Set: e30e52c8-df91-11ea-8231-0050563df028:9-14
Sun Aug 16 19:35:12 2020 - [info] Latest slaves (Slaves that received relay log files to the latest):
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] The oldest binary log file/position on all slaves is mysql-bin.000002:3766
Sun Aug 16 19:35:12 2020 - [info] Retrieved Gtid Set: e30e52c8-df91-11ea-8231-0050563df028:9-14
Sun Aug 16 19:35:12 2020 - [info] Oldest slaves:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.3: Determining New Master Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] Searching new master from slaves..
Sun Aug 16 19:35:12 2020 - [info]  Candidate masters from the configuration file:
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.103(192.168.199.103:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]   192.168.199.104(192.168.199.104:3306)  Version=5.7.28-log (oldest major 
version between slaves) log-bin:enabled
Sun Aug 16 19:35:12 2020 - [info]     GTID ON
Sun Aug 16 19:35:12 2020 - [info]     Replicating from 192.168.199.102(192.168.199.102:3306)
Sun Aug 16 19:35:12 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
Sun Aug 16 19:35:12 2020 - [info]  Non-candidate masters:
Sun Aug 16 19:35:12 2020 - [info]  Searching from candidate_master slaves which have received the latest rel
ay log events..
Sun Aug 16 19:35:12 2020 - [info] New master is 192.168.199.103(192.168.199.103:3306)
Sun Aug 16 19:35:12 2020 - [info] Starting master failover..
Sun Aug 16 19:35:12 2020 - [info] 
From:
192.168.199.102(192.168.199.102:3306) (current master)
 +--192.168.199.103(192.168.199.103:3306)
 +--192.168.199.104(192.168.199.104:3306)

To:
192.168.199.103(192.168.199.103:3306) (new master)
 +--192.168.199.104(192.168.199.104:3306)
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 3.3: New Master Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info]  Waiting all logs to be applied.. 
Sun Aug 16 19:35:12 2020 - [info]   done.
Sun Aug 16 19:35:12 2020 - [info] Getting new master's binlog name and position..
Sun Aug 16 19:35:12 2020 - [info]  mysql-bin.000001:1341
Sun Aug 16 19:35:12 2020 - [info]  All other slaves should start replication from here. Statement should be:
 CHANGE MASTER TO MASTER_HOST='192.168.199.103', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl
ica', MASTER_PASSWORD='xxx';
Sun Aug 16 19:35:12 2020 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: mysql-bin.000001, 1341,
 e30e52c8-df91-11ea-8231-0050563df028:1-14
Sun Aug 16 19:35:12 2020 - [info] Executing master IP activate script:
Sun Aug 16 19:35:12 2020 - [info]   /etc/masterha/scripts/master_ip_failover --command=start --ssh_user=root
 --orig_master_host=192.168.199.102 --orig_master_ip=192.168.199.102 --orig_master_port=3306 --new_master_ho
st=192.168.199.103 --new_master_ip=192.168.199.103 --new_master_port=3306 --new_master_user='mha'   --new_ma
ster_password=xxx
Unknown option: new_master_user
Unknown option: new_master_password

***************************************************************
Enabling the VIP - 192.168.199.105/24 on new master: 192.168.199.103 
***************************************************************

Sun Aug 16 19:35:12 2020 - [info]  OK.
Sun Aug 16 19:35:12 2020 - [info] ** Finished master recovery successfully.
Sun Aug 16 19:35:12 2020 - [info] * Phase 3: Master Recovery Phase completed.
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 4: Slaves Recovery Phase..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] * Phase 4.1: Starting Slaves in parallel..
Sun Aug 16 19:35:12 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info] -- Slave recovery on host 192.168.199.104(192.168.199.104:3306) started, p
id: 11958. Check tmp log /etc/masterha/192.168.199.104_3306_20200816193510.log if it takes time..
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] Log messages from 192.168.199.104 ...
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:12 2020 - [info]  Resetting slave 192.168.199.104(192.168.199.104:3306) and starting replic
ation from the new master 192.168.199.103(192.168.199.103:3306)..
Sun Aug 16 19:35:12 2020 - [info]  Executed CHANGE MASTER.
Sun Aug 16 19:35:13 2020 - [info]  Slave started.
Sun Aug 16 19:35:13 2020 - [info]  gtid_wait(e30e52c8-df91-11ea-8231-0050563df028:1-14) completed on 192.168
.199.104(192.168.199.104:3306). Executed 0 events.
Sun Aug 16 19:35:14 2020 - [info] End of log messages from 192.168.199.104.
Sun Aug 16 19:35:14 2020 - [info] -- Slave on host 192.168.199.104(192.168.199.104:3306) started.
Sun Aug 16 19:35:14 2020 - [info] All new slave servers recovered successfully.
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] * Phase 5: New master cleanup phase..
Sun Aug 16 19:35:14 2020 - [info] 
Sun Aug 16 19:35:14 2020 - [info] Resetting slave info on the new master..
Sun Aug 16 19:35:14 2020 - [info]  192.168.199.103: Resetting slave info succeeded.
Sun Aug 16 19:35:14 2020 - [info] Master failover to 192.168.199.103(192.168.199.103:3306) completed success
fully.
Sun Aug 16 19:35:14 2020 - [info] 

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

app1: MySQL Master failover 192.168.199.102(192.168.199.102:3306) to 192.168.199.103(192.168.199.103:3306) s
ucceeded

Master 192.168.199.102(192.168.199.102:3306) is down!

Check MHA Manager logs at manager:/etc/masterha/manager.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.199.102(192.168.199.102:3306)
Selected 192.168.199.103(192.168.199.103:3306) as a new master.
192.168.199.103(192.168.199.103:3306): OK: Applying all logs succeeded.
192.168.199.103(192.168.199.103:3306): OK: Activated master IP address.
192.168.199.104(192.168.199.104:3306): OK: Slave started, replicating from 192.168.199.103(192.168.199.103:3
306)
192.168.199.103(192.168.199.103:3306): Resetting slave info succeeded.
Master failover to 192.168.199.103(192.168.199.103:3306) completed successfully.
[root@manager masterha]# 
[root@manager masterha]#

你可能感兴趣的:(MHA)

MySQL MHA pokemon.. mysql 数据库
一、MySQLMHA高可用环境概述1.什么是MHAMHA（MasterHighAvailability）是一款用于MySQL数据库集群的高可用解决方案，主要解决MySQL单点故障问题。在MySQL集群的主服务器发生故障时，MHA可以自动执行故障切换，将一个从服务器提升为新的主服务器，最大限度地保证数据的一致性。MHA的切换时间通常在0-30秒之间，极大提高了MySQL集群的可用性。2.MHA的组成
2018.09.28 Betty丽丽
财富目标：9月轻松愉快地显化一万二的财富目标，活在丰盛喜悦之中！计划：1.三大良田2.帮助业力伙伴3.帮助这个世界需要帮助的人行动：1.种下分享智慧的好种子，帮助一个有财富方面匮乏的朋友去做冥想，清理他的负面情绪，让他感受到内心的平和与喜悦，他看到了自己金色的财富之花盛开，非常棒！图片发自App2.种下肯定他人赞美他人的好种子，给班级的同学们带来了一个小游戏叫做iamhappy，让同学们都很开心！
xwiki html和css,MediaWiki vs. XWiki Ake阿科多语言信息技术编程数据库操作系统
140Afar,Abkhazian,Afrikaans,Amharic,Arabic,Assamese,Aymara,Azerbaijani,Bashkir,Byelorussian,Bulgarian,Bihari,Bislama,Bengali;Bangla,Tibetan,Breton,Catalan,Corsican,Czech,Welsh,Danish,German,Bhutani,Gr
mysql mha自动切换_mha+mysql自动切换佐罗先生 mysql mha自动切换
manager:192.168.2.254master:192.168.2.252slave:192.168.2.253VIP:192.168.2.144操作系统：centos6.564位1.配置ssh互信(root用户每台都执行)#ssh-keygen#ssh-copy-id192.168.2.252#ssh-copy-id192.168.2.253#ssh-copy-id192.168.2.2
MySQL-MHA手动切换泰山与水 #MySQL mysql 数据库服务器
环境检查当前数据库集群环境运行状态，包括主从复制状态和SSH能力检查主从复制状态在MHA的manager服务器执行命令：asterha_check_repl--conf={MHA路径}/conf/app.cnf检查主从SSH服务在MHA的manager服务器执行命令：masterha_check_ssh--conf={MHA路径}/conf/app.cnf校验主库和其他从库的GTID一致性获取主从
MHA+MYCAT 高可用架构第九系艾文 linux Linux tools 服务器数据库 mycat mha linux
架构图如下：本次是4服务器架构如下环境：centos7.2x64mariadb10.4MHA5.7MyCat1.6.7IP规划IP功能10.1.41.166VIP10.1.41.167master,mycat,mha.node10.1.41.168slave(master),mha.node10.1.41.165slave,mycat,keepalived10.1.41.169slave,myca
mysql8.0使用MHA实现高可用 Fish_1112 mysql MHA
1.环境配置本实验环境共有四个节点，其角色分配如下（实验机器均为centos7.x）机器名称IP配置服务角色manager172.16.90.211manager控制器master172.16.90.212数据库主服务器slave1172.16.90.213数据库从服务器slave2172.16.90.214数据库从服务器为了方便我们后期的操作，我们在各节点的/etc/hosts文件配置内容中添加
Android Camera原理之camx hal架构_libcamhal 2401_85039631 android 架构
libcamxncs\libstripingLOCAL_WHOLE_STATIC_LIBRARIES:=libcamxdspstreamerlibcamxhwlbpslibcamxgeneratedlibcamxhallibcamxhalutilslibcamxhwlfdlibcamxhwlifelibcamxhwlipelibcamxhwliqmodulelibcamxswlfdmanagerl
MHA高可用配置及故障切换最新小梦 scala 开发语言后端
MHA概述一套优秀的MySQL高可用环境下故障切换和主从复制的软件MySQL故障过程中，MHA能做到0~30秒内自动完成故障切换MHA的组成MHAManager(管理节点)MHANode（数据节点）MHA特点自动故障切换过程中，MHA试图从宕机的主服务器上保存二进制日志，最大程度的保证数据不丢失使用半同步复制，可以大大降低数据丢失的风险目前MHA支持一主多从架构，最少三台服务，即一主两从同步，异步
mysql 8.0 高可用_MySQL 8.0 MGR（组复制）高可用VIP切换脚本错过整个世界 mysql 8.0 高可用
MySQL8.0MGR(组复制)高可用VIP切换脚本发布时间：2020-07-1401:26:18来源：51CTO阅读：1687作者：hcymysqlMySQL8.0MGR(组复制)高可用VIP切换脚本简介：MGR(组复制)官方推荐用MySQLrouter中间件去做MGR高可用故障转移，但其多过了一层网络，性能会下降，并且需要额外维护一套中间件，运维成本过高，于是写了一个类似MHA的master_
python Log篇（Logging） JensenZhong python 基础 python php 开发语言
pythonLog篇（Logging）文章目录pythonLog篇（Logging）一、Logging环境二、我们先了解一下Logging都有哪些信息等级三、文件格式化，a.StreamHandlerb.FileHandlerc.RotatingFileHandlerd.TimedRotatingFileHandler四、日志格式化，让我们显示我们想要显示的数据五、Logging示例一、Loggi
CityHash、FarmHash 秋夫人哈希算法算法数据结构
CityHash和FarmHash都是由Google开发的非加密哈希函数，专为快速处理大量数据而设计。它们在数据中心和大规模分布式系统中尤其有用，用于任务如数据分区、查找优化、数据校验等。这两种哈希函数都以其高效的性能和良好的分布特性而著称。CityHashCityHash是一系列哈希函数的集合，专门优化用于哈希字符串。它提供了多种版本，如CityHash32、CityHash64和CityHas
2023-02-11 俗世尘沙
正文Theslowdeathofsurveillancecapitalismhasbegun“监控资本主义”已经开始缓慢死亡Surveillancecapitalismjustgotakicking.Inanultimatum,theEuropeanUnionhasdemandedthatMetareformitsapproachtopersonalizedadvertising—aseeming
md5哈希c语言程序,【笔记】C Sharp哈希值计算MD5 娜携年华 md5哈希c语言程序
[C#]纯文本查看复制代码publicdelegatevoidAsyncCheckHeadler(AsyncCheckEventArgse);publicclassMD5Checker{//支持所有哈希算法privatestaticHashAlgorithmhashAlgorithm;//文件缓冲区privatestaticbyte[]buffer;//文件读取流privatestaticStre
VBA之正则表达式（8）-- 重复字符分组 taller_2000 VBA 数组工作表 Excel 正则正则数组 Split 替换重复
实例需求：数据保存在A列中，需要将其中重复字符分拆后保存在后续的列中，为简化示例代码，只考虑小写英文字符。这个需求也并不复杂，用VBA代码逐个判断字符和其前后的字符对比，就可以区分每组，高手可以写出递归调用过程。用正则处理这种问题会更简单。SubRegExpDemo()DimstrTxtAsStringDimobjRegExAsObject,objMatchAsObjectDimobjMHAsOb
Verilog刷题笔记60 十六追梦记笔记 fpga开发
题目：Exams/2013q2bfsmConsiderafinitestatemachinethatisusedtocontrolsometypeofmotor.TheFSMhasinputsxandy,whichcomefromthemotor,andproducesoutputsfandg,whichcontrolthemotor.Thereisalsoaclockinputcalledclk
Java中HashSet和HashMap类之间的区别 cumt30111 数据结构 java python mysql 队列
HashMap与HashSet(HashMapvsHashSet)First,wewillseehowHashMapdiffersfromHashSetinJava?首先，我们将看到HashMap与Java中的HashSet有何不同？哈希图(HashMap)Thisclassisavailableinjava.utilpackage.此类在java.util包中可用。Thisclassisanim
【codeforces 115E】Linear Kingdom Races 题意&题解&代码（c++） deritt oi之路 DERIT的博客专栏线段树-dp
**E.LinearKingdomRaces**timelimitpertest5secondsmemorylimitpertest256megabytesYouareacarraceorganizerandwouldliketoarrangesomeracesinLinearKingdom.LinearKingdomhasnconsecutiveroadsspanningfromlefttori
具有手势识别的动捕设备——mHand Pro VR数据手套广州虚拟动力-动捕&虚拟主播 vr 动作捕捉数据手套 vr 3d 科技游戏引擎 unity ue4 udp
数据手套是指通过手套内置的传感器，实时采集手部运动数据的动捕设备，通常被应用于虚拟仿真、虚拟现实vr交互、动画制作等领域。其中，基于惯性动作捕捉技术研发的数据手套，凭借其高性价比的优势，在市面上的应用更为广泛。如mHandPro数据手套，其基本原理是通过手部的传感器、震动器和反馈装置，实时捕捉真人的手部动作、力度和触感反馈，从而让真人可以在虚拟空间中进行真实感十足的手部互动，为用户提供了一种身临其
keepalived mysql双主架构图_MySQL双主+keepalived实现高可用如果有片海 keepalived mysql双主架构图
mysql+keepalived实现高可用+主主复制模式为了解决mysql的单点故障问题，衍生出很多mysql的高可用方案：keepalived+双主、MHA、PXC、MMM、Hearbeat+DRBD等，比较常用的一般是keepalived+双主，MHA和PXC在此搭建实验环境，实现keepalived+mysql双主模式。实验思路：两台MySQL互为主从关系(双主)，通过keepalived配
More important thing is Ability 鱿鱼儿
图片发自AppIfoneaspiretowearthecaptain'scapandnavigatetheshipofbusiness,personalityandtheabilitytotalkaremoreimportantthanaknowledgeofLatinverbsorashipskinfromHarvard.
Mysql数据库MariaDB数据库MHA高可用程序 yichen_china
声明：本次实验使用的是MariaDB数据库，所以本文中所出现的MariaDB与MySQL都是指的是MariaDB！！！MHA（MasterHA）是一款开源的MySQL的高可用程序，它为MySQL主从复制架构提供了automatingmasterfailover功能。MHA在监控到master节点故障时，会提升其中拥有最新数据的slave节点成为新的master节点，在此期间，MHA会通过于其它从节
构建jdk1.8+ffmpeg镜像 wcy10086 ffmpeg docker jdk
FROMharbor.**.cn/library/jdk1.8:v2.0MAINTAINERwcyRUNyuminstall-yepel-releaseRUNrpm--importhttp://li.nux.ro/download/nux/RPM-GPG-KEY-nux.roRUNrpm-Uvhhttp://li.nux.ro/download/nux/dextop/el7/x86_64/nux-
mysql数据导出、导入皮不动 #mysql mysql 数据库
导出数据select*INTOOUTFILE'/xxx/mysql_export.csv'FIELDSTERMINATEDBY','ENCLOSEDBY'"'LINESTERMINATEDBY'\n'FROMhal;INTOOUTFILE''：将查询结果输出到指定文件路径FIELDSTERMINATEDBY','：指定字段（或列）间的分隔符为逗号（,）ENCLOSEDBY'"'：指定每个字段值应该
Mysql运维篇（六）部署MHA--一主二从部署董乐，快乐的乐！运维
一路走来，所有遇到的人，帮助过我的、伤害过我的都是朋友，没有一个是敌人。如有侵权，请留言，我及时删除！MAH架构图一、上传MySQL软件1、同步MySQL软件[root@mysql01~]#ls-lrttotal626112-rw-r--r--.1rootroot641127384Jan3015:13mysql-5.7.20-linux-glibc2.12-x86_64.tar.gz-rw----
英文圆体字练习 2018.03.15 JessicaH2017
Einsteinwaswrongwhenhesaid‘Goddoesnotplaydice’.Considerationofblackholessuggests,notonlythatGoddoesplaydice,butthatHesometimesconfusesusbythrowingthemwheretheycan’tbeseen.—StephenWilliamHawking爱因斯坦说“上
详解MySQL高可用方案--MySQL MHA架构、原理、应用场景等君子愁
概述MySQL高可用，顾名思义就是当MySQL主机或服务发生任何故障时能够立马有其他主机顶替其工作，并且最低要求是要保证数据一致性。因此，对于一个MySQL高可用系统需要达到的目标有以下几点：数据一致性保证--这个是最基本的同时也是前提，如果主备的数据不一致，那么切换就无法进行，当然这里的一致性也是一个相对的，但是要做到最终一致性。故障快速切换--当master故障时这里可以是机器故障或者是实例故
测试环境搭建整套大数据系统（三：搭建集群zookeeper，hdfs，mapreduce，yarn，hive）宇智波云大数据项目 zookeeper hdfs mapreduce hive
一：搭建zkhttps://blog.csdn.net/weixin_43446246/article/details/123327143二：搭建hadoop，yarn，mapreduce。1.安装hadoop。sudotar-zxvfhadoop-3.2.4.tar.gz-C/opt2.修改java配置路径。cd/opt/hadoop-3.2.4/etc/hadoopvimhadoop-env.
待处理的研究内容苏金标 android
android是不是可以在子线程中更新UI回答是可以的android之所以不能在子线程中更新Ui是因为requestLayout会重新测量布局，走了ViewRoot的一系列方法，也会走ViewRootImp的requestLayout()publicvoidrequestLayout(){if(!mHandlingLayoutInLayoutRequest){checkThread();//检测线
快速计算距离Annoy算法原理及Python使用召唤师的峡谷机器学习算法
快速计算距离Annoy算法基本原理高维稀疏数据进行快速相似查找，可以采用learningtohash参考：Minhashing&LSH&Simhash技术汇总,但高维稠密数据查找则采用annoy如何从海量文本中快速查找出相似的TopN文本Annoy（ApproximateNearestNeighborsOhYeah）快速算法,在实际应用中发现无论计算速度和准确性都非常不错。原始2D数据分布图：1.
数据采集高并发的架构应用 3golden .net
问题的出发点：最近公司为了发展需要，要扩大对用户的信息采集，每个用户的采集量估计约2W。如果用户量增加的话，将会大量照成采集量成3W倍的增长，但是又要满足日常业务需要，特别是指令要及时得到响应的频率次数远大于预期。 &n
不停止 MySQL 服务增加从库的两种方式 brotherlamp linux linux视频 linux资料 linux教程 linux自学
现在生产环境MySQL数据库是一主一从，由于业务量访问不断增大，故再增加一台从库。前提是不能影响线上业务使用，也就是说不能重启MySQL服务，为了避免出现其他情况，选择在网站访问量低峰期时间段操作。一般在线增加从库有两种方式，一种是通过mysqldump备份主库，恢复到从库，mysqldump是逻辑备份，数据量大时，备份速度会很慢，锁表的时间也会很长。另一种是通过xtrabacku
Quartz——SimpleTrigger触发器 eksliang SimpleTrigger TriggerUtils quartz
转载请出自出处：http://eksliang.iteye.com/blog/2208166 一.概述 SimpleTrigger触发器，当且仅需触发一次或者以固定时间间隔周期触发执行；二.SimpleTrigger的构造函数 SimpleTrigger(String name, String group)：通过该构造函数指定Trigger所属组和名称； Simpl
Informatica应用（1） 18289753290 sql workflow lookup 组件 Informatica
1.如果要在workflow中调用shell脚本有一个command组件，在里面设置shell的路径；调度wf可以右键出现schedule，现在用的是HP的tidal调度wf的执行。 2.designer里面的router类似于SSIS中的broadcast（多播组件）;Reset_Workflow_Var：参数重置（比如说我这个参数初始是1在workflow跑得过程中变成了3我要在结束时还要
python 获取图片验证码中文字酷的飞上天空 python
根据现成的开源项目 http://code.google.com/p/pytesser/改写在window上用easy_install安装不上看了下源码发现代码很少于是就想自己改写一下添加支持网络图片的直接解析 #coding:utf-8 #import sys #reload(sys) #sys.s
AJAX 永夜-极光 Ajax
1.AJAX功能:动态更新页面,减少流量消耗,减轻服务器负担 2.代码结构: <html> <head> <script type="text/javascript"> function loadXMLDoc() { .... AJAX script goes here ...
创业OR读研随便小屋创业
现在研一，有种想创业的想法，不知道该不该去实施。因为对于的我情况这两者是矛盾的，可能就是鱼与熊掌不能兼得。研一的生活刚刚过去两个月，我们学校主要的是
需求做得好与坏直接关系着程序员生活质量 aijuans IT 生活
这个故事还得从去年换工作的事情说起，由于自己不太喜欢第一家公司的环境我选择了换一份工作。去年九月份我入职现在的这家公司，专门从事金融业内软件的开发。十一月份我们整个项目组前往北京做现场开发，从此苦逼的日子开始了。系统背景：五月份就有同事前往甲方了解需求一直到6月份，后续几个月也完
如何定义和区分高级软件开发工程师 aoyouzi
在软件开发领域，高级开发工程师通常是指那些编写代码超过 3 年的人。这些人可能会被放到领导的位置，但经常会产生非常糟糕的结果。Matt Briggs 是一名高级开发工程师兼 Scrum 管理员。他认为，单纯使用年限来划分开发人员存在问题，两个同样具有 10 年开发经验的开发人员可能大不相同。近日，他发表了一篇博文，根据开发者所能发挥的作用划分软件开发工程师的成长阶段。　　初
Servlet的请求与响应百合不是茶 servlet get提交 java处理post提交
Servlet是tomcat中的一个重要组成,也是负责客户端和服务端的中介 1,Http的请求方式(get ,post); 客户端的请求一般都会都是Servlet来接受的,在接收之前怎么来确定是那种方式提交的,以及如何反馈,Servlet中有相应的方法, http的get方式 servlet就是都doGet(
web.xml配置详解之listener bijian1013 java web.xml listener
一.定义 <listener> <listen-class>com.myapp.MyListener</listen-class> </listener> 二.作用该元素用来注册一个监听器类。可以收到事件什么时候发生以及用什么作为响
Web页面性能优化（yahoo技术） Bill_chen JavaScript Ajax Web css Yahoo
1.尽可能的减少HTTP请求数 content 2.使用CDN server 3.添加Expires头(或者 Cache-control) server 4.Gzip 组件 server 5.把CSS样式放在页面的上方。 css 6.将脚本放在底部(包括内联的) javascript 7.避免在CSS中使用Expressions css 8.将javascript和css独立成外部文
【MongoDB学习笔记八】MongoDB游标、分页查询、查询结果排序 bit1129 mongodb
游标游标，简单的说就是一个查询结果的指针。游标作为数据库的一个对象，使用它是包括声明打开循环抓去一定数目的文档直到结果集中的所有文档已经抓取完关闭游标游标的基本用法，类似于JDBC的ResultSet(hasNext判断是否抓去完,next移动游标到下一条文档)，在获取一个文档集时，可以提供一个类似JDBC的FetchSize
ORA-12514 TNS 监听程序当前无法识别连接描述符中请求服务的解决方法白糖_ ORA-12514
今天通过Oracle SQL*Plus连接远端服务器的时候提示“监听程序当前无法识别连接描述符中请求服务”，遂在网上找到了解决方案： ①打开Oracle服务器安装目录\NETWORK\ADMIN\listener.ora文件，你会看到如下信息： # listener.ora Network Configuration File: D:\database\Oracle\net
Eclipse 问题 A resource exists with a different case bozch eclipse
在使用Eclipse进行开发的时候，出现了如下的问题： Description Resource Path Location TypeThe project was not built due to "A resource exists with a different case: '/SeenTaoImp_zhV2/bin/seentao'.&
编程之美-小飞的电梯调度算法 bylijinnan 编程之美
public class AptElevator { /** * 编程之美小飞电梯调度算法 * 在繁忙的时间，每次电梯从一层往上走时，我们只允许电梯停在其中的某一层。 * 所有乘客都从一楼上电梯，到达某层楼后，电梯听下来，所有乘客再从这里爬楼梯到自己的目的层。 * 在一楼时，每个乘客选择自己的目的层，电梯则自动计算出应停的楼层。 * 问：电梯停在哪
SQL注入相关概念 chenbowen00 sql Web 安全
SQL Injection：就是通过把SQL命令插入到Web表单递交或输入域名或页面请求的查询字符串，最终达到欺骗服务器执行恶意的SQL命令。具体来说，它是利用现有应用程序，将（恶意）的SQL命令注入到后台数据库引擎执行的能力，它可以通过在Web表单中输入（恶意）SQL语句得到一个存在安全漏洞的网站上的数据库，而不是按照设计者意图去执行SQL语句。首先让我们了解什么时候可能发生SQ
[光与电]光子信号战防御原理 comsci 原理
无论是在战场上,还是在后方,敌人都有可能用光子信号对人体进行控制和攻击,那么采取什么样的防御方法,最简单,最有效呢? 我们这里有几个山寨的办法,可能有些作用,大家如果有兴趣可以去实验一下根据光
oracle 11g新特性:Pending Statistics daizj oracle dbms_stats
oracle 11g新特性:Pending Statistics 转从11g开始，表与索引的统计信息收集完毕后，可以选择收集的统信息立即发布，也可以选择使新收集的统计信息处于pending状态，待确定处于pending状态的统计信息是安全的，再使处于pending状态的统计信息发布，这样就会避免一些因为收集统计信息立即发布而导致SQL执行计划走错的灾难。在 11g 之前的版本中，D
快速理解RequireJs dengkane jquery requirejs
RequireJs已经流行很久了，我们在项目中也打算使用它。它提供了以下功能：声明不同js文件之间的依赖可以按需、并行、延时载入js库可以让我们的代码以模块化的方式组织初看起来并不复杂。在html中引入requirejs 在HTML中，添加这样的 <script> 标签： <script src="/path/to
C语言学习四流程控制if条件选择、for循环和强制类型转换 dcj3sjt126com c
# include <stdio.h> int main(void) { int i, j; scanf("%d %d", &i, &j); if (i > j) printf("i大于j\n"); else printf("i小于j\n"); retu
dictionary的使用要注意 dcj3sjt126com IO
NSDictionary *dict = [NSDictionary dictionaryWithObjectsAndKeys: user.user_id , @"id", user.username , @"username",
Android 中的资源访问(Resource) finally_m xml android String drawable color
简单的说，Android中的资源是指非代码部分。例如，在我们的Android程序中要使用一些图片来设置界面，要使用一些音频文件来设置铃声，要使用一些动画来显示特效，要使用一些字符串来显示提示信息。那么，这些图片、音频、动画和字符串等叫做Android中的资源文件。在Eclipse创建的工程中，我们可以看到res和assets两个文件夹，是用来保存资源文件的，在assets中保存的一般是原生
Spring使用Cache、整合Ehcache 234390216 spring cache ehcache @Cacheable
Spring使用Cache 从3.1开始，Spring引入了对Cache的支持。其使用方法和原理都类似于Spring对事务管理的支持。Spring Cache是作用在方法上的，其核心思想是这样的：当我们在调用一个缓存方法时会把该方法参数和返回结果作为一个键值对存放在缓存中，等到下次利用同样的
当druid遇上oracle blob(clob) jackyrong oracle
http://blog.csdn.net/renfufei/article/details/44887371 众所周知，Oracle有很多坑, 所以才有了去IOE。在使用Druid做数据库连接池后，其实偶尔也会碰到小坑，这就是使用开源项目所必须去填平的。【如果使用不开源的产品，那就不是坑，而是陷阱了，你都不知道怎么去填坑】用Druid连接池，通过JDBC往Oracle数据库的
easyui datagrid pagination获得分页页码、总页数等信息 ldzyz007
var grid = $('#datagrid'); var options = grid.datagrid('getPager').data("pagination").options; var curr = options.pageNumber; var total = options.total; var max =
浅析awk里的数组 nigelzeng 二维数组 array 数组 awk
awk绝对是文本处理中的神器，它本身也是一门编程语言，还有许多功能本人没有使用到。这篇文章就单单针对awk里的数组来进行讨论，如何利用数组来帮助完成文本分析。有这么一组数据： abcd,91#31#2012-12-31 11:24:00 case_a,136#19#2012-12-31 11:24:00 case_a,136#23#2012-12-31 1
搭建 CentOS 6 服务器(6) - TigerVNC rensanning centos
安装GNOME桌面环境 # yum groupinstall "X Window System" "Desktop" 安装TigerVNC # yum -y install tigervnc-server tigervnc 启动VNC服务 # /etc/init.d/vncserver restart # vncser
Spring 数据库连接整理 tomcat_oracle spring bean jdbc
1、数据库连接jdbc.properties配置详解　　jdbc.url=jdbc:hsqldb:hsql://localhost/xdb 　　jdbc.username=sa 　　jdbc.password= 　　jdbc.driver=不同的数据库厂商驱动，此处不一一列举　　接下来，详细配置代码如下：　　 Spring连接池
Dom4J解析使用xpath java.lang.NoClassDefFoundError: org/jaxen/JaxenException异常 xp9802
用Dom4J解析xml,以前没注意,今天使用dom4j包解析xml时在xpath使用处报错异常栈：java.lang.NoClassDefFoundError: org/jaxen/JaxenException异常导入包 jaxen-1.1-beta-6.jar 解决; &nb