minimonster
minimonster

MHA + keepalived mysql高可用方案部署

目录

    原理

    安装mysql主从

    安装mha

    测试切换

    恢复故障

    增加keepalive，避免跨网段无法访问虚地址    


原理

        master出现故障时，可以自动把最新数据的slave提升为新的master，把所有其他的slave重新指向新的master。切换过程对应用程序透明。迁移时间20-30秒左右。

        自动切换过程中，mha尝试从原master保存binlog，最大程度保证数据不丢失，如果服务器宕机（无法ssh连接），mha无法保存二进制日志，只进行故障转移丢失少量最新数据。
        使用mysql5.5版半同步机制可以大大降低数据丢失风险。如果只有一个slave收到最新的binlog，会同步数据到所有slave，保证所有节点的数据一致性。


部署信息

    主 10.78.72.73 centos6.5
    从1(备主) 10.78.72.74 centos6.5
    从2 10.78.72.75 centos6.5
    管理节点 10.78.72.76 centos7
    VIP 10.78.72.77


安装mysql主从

# 1主2从 安装mysql（版本：Ver 14.14 Distrib 5.1.71, for redhat-linux-gnu (x86_64) using readline 5.1）
[root@mysql01 ~]# yum install mysql mysql-server mysql-libs mysql-devel -y

# 配置文件

# 另外两个将server-id修改为不同值

[root@ mysql01 ~]# cat /etc/my.cnf  | grep -v '^$' | grep -v '^#'
[client]
port            = 3306
socket          = /var/lib/mysql/mysql.sock
[mysqld]
port            = 3306
socket          = /var/lib/mysql/mysql.sock
skip-external-locking
key_buffer_size = 256M
max_allowed_packet = 1M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
thread_concurrency = 8
wait_timeout = 10
max_connections = 1000
log-bin=mysql-bin
relay-log=relay-bin
relay-log-index=relay-bin-index
binlog-ignore-db=mysql
replicate-ignore-db=mysql
lower_case_table_names = 1
skip-name-resolve
binlog_format=mixed
log-slave-updates
relay_log_purge=0
read_only=1
server-id       = 1
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
[myisamchk]
key_buffer_size = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout

# 启动mysql
# /etc/init.d/mysqld start

# 设置slave01、slave02主从同步
# 在master上创建复制用户（允许从使用repl登录）
grant replication slave, file, select on *.* to 'repl'@'10.78.72.74' identified by 'xxxxx';
grant replication slave, file, select on *.* to 'repl'@'10.78.72.75' identified by 'xxxxx';
flush privileges;

# 在备master上创建复制用户（允许从使用repl登录） （不要忘记，否则切换到这个的时候没法同步）
grant replication slave, file, select on *.* to 'repl'@'10.78.72.73' identified by 'xxxxx';
grant replication slave, file, select on *.* to 'repl'@'10.78.72.75' identified by 'xxxxx';
flush privileges;

# 在master上查询
mysql> show master status;
+------------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000003 | 663 | | mysql |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

# 在slave01上同步
mysql> STOP SLAVE;
mysql> RESET SLAVE;
mysql> CHANGE MASTER TO MASTER_HOST='10.78.72.73',
MASTER_USER='repl',
MASTER_PASSWORD='xxxxx',
MASTER_LOG_FILE='mysql-bin.000003',
MASTER_LOG_POS=663;
mysql> START SLAVE;
mysql> SHOW SLAVE STATUS \G

# 在slave02上同步
mysql> STOP SLAVE;
mysql> RESET SLAVE;
mysql> CHANGE MASTER TO MASTER_HOST='10.78.72.73',
MASTER_USER='repl',
MASTER_PASSWORD='xxxxx',
MASTER_LOG_FILE='mysql-bin.000003',
MASTER_LOG_POS=663;
mysql> START SLAVE;
mysql> SHOW SLAVE STATUS \G

安装mha

设置免密码登录
# 在master、slave、manager上做免密登录
# master
ssh-keygen -t rsa
一直回车
ssh [email protected] "cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys" < ~/.ssh/id_rsa.pub
ssh [email protected] "cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys" < ~/.ssh/id_rsa.pub
ssh [email protected] "cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys" < ~/.ssh/id_rsa.pub

# slave
...

# manager
...

创建mha复制账号
# 在master、slave01、salve02上创建mha复制账号（mha_rep）
grant all privileges on *.* to 'mha_rep'@'10.78.72.73' identified by 'xxxxx';
grant all privileges on *.* to 'mha_rep'@'10.78.72.74' identified by 'xxxxx';
grant all privileges on *.* to 'mha_rep'@'10.78.72.75' identified by 'xxxxx';
grant all privileges on *.* to 'mha_rep'@'10.78.72.76' identified by 'xxxxx';
flush privileges;

安装包
# 在master、slave01、slave02、manager上安装mha4mysql-node包
# yum install perl-DBD-MySQL -y
# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm
Preparing... ########################################### [100%]
1:mha4mysql-node ########################################### [100%]

# 用于识别差异日志并应用于其他slave
# cp /usr/bin/apply_diff_relay_logs /usr/local/bin/

# 用于保存和复制二进制日志
# cp /usr/bin/save_binary_logs /usr/local/bin/

# cp /usr/bin/filter_mysqlbinlog /usr/local/bin/

# 用于清除中继日志
# cp /usr/bin/purge_relay_logs /usr/local/bin/

# master安装manager
# yum install epel-release -y && yum clean all && yum makecache
# yum install perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Time-HiRes -y
# tar -xf mha4mysql-manager-0.56.tar.gz && cd mha4mysql-manager-0.56
[root@manager01 mha4mysql-manager-0.56]# yum install perl* -y && perl Makefile.PL && make && make install

# 复制脚本
[root@manager01]# cp /usr/bin/masterha_* /usr/local/bin/

# 查看masterha脚本
# ll /usr/local/bin/
total 84
-rwxr-xr-x 1 root root 16367 May 7 11:27 apply_diff_relay_logs
-rwxr-xr-x 1 root root 4807 May 7 11:27 filter_mysqlbinlog
-r-xr-xr-x 1 root root 1995 May 7 11:41 masterha_check_repl
-r-xr-xr-x 1 root root 1779 May 7 11:41 masterha_check_ssh
-r-xr-xr-x 1 root root 1865 May 7 11:41 masterha_check_status
-r-xr-xr-x 1 root root 3201 May 7 11:41 masterha_conf_host
-r-xr-xr-x 1 root root 2517 May 7 11:41 masterha_manager
-r-xr-xr-x 1 root root 2165 May 7 11:41 masterha_master_monitor
-r-xr-xr-x 1 root root 2373 May 7 11:41 masterha_master_switch
-r-xr-xr-x 1 root root 5171 May 7 11:41 masterha_secondary_check
-r-xr-xr-x 1 root root 1739 May 7 11:41 masterha_stop
-rwxr-xr-x 1 root root 8261 May 7 11:27 purge_relay_logs
-rwxr-xr-x 1 root root 7525 May 7 11:27 save_binary_logs

配置manager
# mkdir -p /etc/mha/ && cp samples/conf/app1.cnf /etc/mha/
# mkdir -p /var/log/masterha/app1
# mkdir -p /etc/mha/scripts

# 配置文件
# cat /etc/mha/app1.cnf
[server default]
manager_workdir=/var/log/masterha/app1
manager_log=/var/log/masterha/app1/manager.log
user=mha_rep # MHA管理mysql的用户名
password=xxxxx                         # MHA管理mysql的密码
ssh_user=root # 免密码登录的用户名
repl_user=repl # 主从复制账号名
repl_password=xxxxx                         # 主从复制账号密码
ping_interval=1 # 用来检查master是否正常

[server1]
hostname=10.78.72.73
candidate_master=1 # master宕机后，优先启用这台作为master

[server2]
hostname=10.78.72.74
candidate_master=1 # master宕机后，优先启用这台作为master

[server3]
hostname=10.78.72.75
no_master=1 # 使服务器不能成为master


# 测试ssh互信
[deploy@manager01 ~]$ masterha_check_ssh --conf=/etc/mha/app1.cnf
Mon May 7 13:53:40 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon May 7 13:53:40 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Mon May 7 13:53:40 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..
Mon May 7 13:53:40 2018 - [info] Starting SSH connection tests..
Mon May 7 13:53:41 2018 - [debug]
Mon May 7 13:53:40 2018 - [debug] Connecting via SSH from [email protected](10.78.72.73:22) to [email protected](10.78.72.74:22)..
Mon May 7 13:53:40 2018 - [debug] ok.
Mon May 7 13:53:40 2018 - [debug] Connecting via SSH from [email protected](10.78.72.73:22) to [email protected](10.78.72.75:22)..
Mon May 7 13:53:40 2018 - [debug] ok.
Mon May 7 13:53:41 2018 - [debug]
Mon May 7 13:53:41 2018 - [debug] Connecting via SSH from [email protected](10.78.72.74:22) to [email protected](10.78.72.73:22)..
Mon May 7 13:53:41 2018 - [debug] ok.
Mon May 7 13:53:41 2018 - [debug] Connecting via SSH from [email protected](10.78.72.74:22) to [email protected](10.78.72.75:22)..
Mon May 7 13:53:41 2018 - [debug] ok.
Mon May 7 13:53:42 2018 - [debug]
Mon May 7 13:53:41 2018 - [debug] Connecting via SSH from [email protected](10.78.72.75:22) to [email protected](10.78.72.73:22)..
Mon May 7 13:53:41 2018 - [debug] ok.
Mon May 7 13:53:41 2018 - [debug] Connecting via SSH from [email protected](10.78.72.75:22) to [email protected](10.78.72.74:22)..
Mon May 7 13:53:41 2018 - [debug] ok.
Mon May 7 13:53:42 2018 - [info] All SSH connection tests passed successfully.

# 测试mysql主从复制是否成功
[deploy@manager01 ~]$ masterha_check_repl --conf=/etc/mha/app1.cnf
Mon May 7 14:12:13 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon May 7 14:12:13 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Mon May 7 14:12:13 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..
Mon May 7 14:12:13 2018 - [info] MHA::MasterMonitor version 0.56.
Mon May 7 14:12:14 2018 - [info] GTID failover mode = 0
Mon May 7 14:12:14 2018 - [info] Dead Servers:
Mon May 7 14:12:14 2018 - [info] Alive Servers:
Mon May 7 14:12:14 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Mon May 7 14:12:14 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Mon May 7 14:12:14 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Mon May 7 14:12:14 2018 - [info] Alive Slaves:
Mon May 7 14:12:14 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Mon May 7 14:12:14 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Mon May 7 14:12:14 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Mon May 7 14:12:14 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Mon May 7 14:12:14 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Mon May 7 14:12:14 2018 - [info] Not candidate for the new Master (no_master is set)
Mon May 7 14:12:14 2018 - [info] Current Alive Master: 10.78.72.73(10.78.72.73:3306)
Mon May 7 14:12:14 2018 - [info] Checking slave configurations..
Mon May 7 14:12:15 2018 - [info] Checking replication filtering settings..
Mon May 7 14:12:15 2018 - [info] binlog_do_db= , binlog_ignore_db= mysql
Mon May 7 14:12:15 2018 - [info] Replication filtering check ok.
Mon May 7 14:12:15 2018 - [info] GTID (with auto-pos) is not supported
Mon May 7 14:12:15 2018 - [info] Starting SSH connection tests..
Mon May 7 14:12:16 2018 - [info] All SSH connection tests passed successfully.
Mon May 7 14:12:16 2018 - [info] Checking MHA Node version..
Mon May 7 14:12:16 2018 - [info] Version check ok.
Mon May 7 14:12:16 2018 - [info] Checking SSH publickey authentication settings on the current master..
Mon May 7 14:12:16 2018 - [info] HealthCheck: SSH to 10.78.72.73 is reachable.
Mon May 7 14:12:17 2018 - [info] Master MHA Node version is 0.56.
Mon May 7 14:12:17 2018 - [info] Checking recovery script configurations on 10.78.72.73(10.78.72.73:3306)..
Mon May 7 14:12:17 2018 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --start_file=mysql-bin.000003
Mon May 7 14:12:17 2018 - [info] Connecting to [email protected](10.78.72.73: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.000003
Mon May 7 14:12:17 2018 - [info] Binlog setting check done.
Mon May 7 14:12:17 2018 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Mon May 7 14:12:17 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha_rep' --slave_host=10.78.72.74 --slave_ip=10.78.72.74 --slave_port=3306 --workdir=/var/tmp --target_version=5.1.71-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Mon May 7 14:12:17 2018 - [info] Connecting to [email protected](10.78.72.74: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.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Mon May 7 14:12:17 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha_rep' --slave_host=10.78.72.75 --slave_ip=10.78.72.75 --slave_port=3306 --workdir=/var/tmp --target_version=5.1.71-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Mon May 7 14:12:17 2018 - [info] Connecting to [email protected](10.78.72.75: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.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Mon May 7 14:12:17 2018 - [info] Slaves settings check done.
Mon May 7 14:12:17 2018 - [info]
10.78.72.73(10.78.72.73:3306) (current master)
+--10.78.72.74(10.78.72.74:3306)
+--10.78.72.75(10.78.72.75:3306)

Mon May 7 14:12:17 2018 - [info] Checking replication health on 10.78.72.74..
Mon May 7 14:12:17 2018 - [info] ok.
Mon May 7 14:12:17 2018 - [info] Checking replication health on 10.78.72.75..
Mon May 7 14:12:17 2018 - [info] ok.
Mon May 7 14:12:17 2018 - [warning] master_ip_failover_script is not defined.
Mon May 7 14:12:17 2018 - [warning] shutdown_script is not defined.
Mon May 7 14:12:17 2018 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.
[deploy@manager01 ~]$

# 注意事项
log-slave-updates // 只有从库开启log_slave_updates时，从库binlog才会记录主库同步的操作日志。
// 默认为1，mysql主从默认从库的relay logs会在SQL线程执行完毕后被自动删除，对于MHA场景下，对于某些滞后从库的恢复依赖于其他从库的relaylog，因此需要采用自动删除功能以及定期清理。清理过多过大的relay log需要注意引起的复制延迟资源开销。MHA通过purge_relay_logs脚本配合cronjob完成。
// https://blog.csdn.net/leshami/article/details/45688503
relay_log_purge=0
read_only=1 // 防止误写，在mha将slave切换为master时，会自动设置read_only=0


所有slave设置purge
# mysql数据库主从复制在默认情况下从库的relay logs会在SQL线程执行完毕后被自动删除
# 但是对于MHA场景下，对于某些滞后从库的恢复依赖其他从库的relay log，因此采用自动删除功能以及定期清理。
# 对于过多过大的relay log需要注意引起的复制延迟资源开销等。
# MHA通过purge_relay_logs脚本配合crontab完成

mkdir -p /var/log/masterha/
crontab -e
# 每天凌晨5点调用purge_relay_logs
0 5 * * * /usr/bin/purge_relay_logs --user=root --disable_relay_log_purge >> /var/log/masterha/purge_relay_logs.log 2>&1

测试切换

增加VIP

mha检测failover的源码文件
/usr/local/share/perl5/MHA/MasterFailover.pm
333行，关注发送stopssh命令，和发送stop命令的命令行参数
在master_ip_failover脚本中处理逻辑不同，
在发送stopssh命令时，原master ssh是通的（手动关闭mysql，但是ssh服务可连）
发送stop命令时，检测原master ssh不通，所以不需要执行ssh命令删除VIP（服务器重启的情况）

脚本：
[root@manager01 app1]# cat /etc/mha/scripts/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 = '10.78.72.77'; #vip地址
my $key = '1';
my $ssh_start_vip = "/sbin/ifconfig eth0:$key $vip netmask 255.255.255.0"; #绑定在指定的网卡上面
my $ssh_stop_vip = "/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,
);
exit &main();
sub main {
print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";
if ( $command eq "stop" || $command eq "stopssh" ) {
my $exit_code = 1;
eval {
print "Disabling the VIP on old master: $orig_master_host \n";
# stopssh命令才去执行stop vip
if ($command eq "stopssh") {
&stop_vip();
}
$exit_code = 0;
};
if ($@) {
warn "Got Error: $@\n";
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "start" ) {
my $exit_code = 10;
eval {
print "Enabling the VIP - $vip on the new master - $new_master_host \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";
exit 0;
}
else {
&usage();
exit 1;
}
}
sub start_vip() {
`ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`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@manager01 app1]#

配置文件增加脚本配置：
[root@manager01 app1]# cat /etc/mha/app1.cnf
[server default]
manager_workdir=/var/log/masterha/app1
manager_log=/var/log/masterha/app1/manager.log
master_ip_failover_script=/etc/mha/scripts/master_ip_failover
user=mha_rep
password=xxxxx
ssh_user=root
repl_user=repl
repl_password=xxxxx
ping_interval=1

[server1]
hostname=10.78.72.73
candidate_master=1

[server2]
hostname=10.78.72.74
candidate_master=1

[server3]
hostname=10.78.72.75
no_master=1

增加VIP
# 在master上添加vip 10.78.72.77， 命令行new_master_host=注意替换
[root@manager01 app1]# /etc/mha/scripts/master_ip_failover --command=start --ssh_user=root --new_master_host=10.78.72.73


确认删除failover文件
[root@manager01 ~]# ls /var/log/masterha/app1/
[root@manager01 ~]# rm /var/log/masterha/app1/app1.failover.error -f


批量写入数据库测试
创建测试账号、测试库
grant all privileges on *.* to 'test'@'%' identified by 'test';
flush privileges;
# 注意上面两句需要在 master 和 slave-mater上都要执行，否则切换后无法写入slave-master
CREATE DATABASE fortest;
USE fortest;
CREATE TABLE number ( num int NOT NULL, PRIMARY KEY (num) );

[root@manager01 ~]# yum install php php-mysql -y
[root@manager01 ~]# cat write.php

date_default_timezone_set('PRC');

// 注意修改VIP
define('DB_HOST', '10.78.72.77');
define('DB_USER', 'test');
define('DB_PASS', 'test');
define('DB_NAME', 'fortest');
$dbc = mysqli_connect(DB_HOST, DB_USER, DB_PASS, DB_NAME) or die();
mysqli_query($dbc, "SET NAMES 'UTF8'");

// 查询已插入数据行数
$query = "select * from number order by num desc limit 1";
$datas = mysqli_query($dbc, $query) or die(mysqli_error($dbc));
$task = mysqli_fetch_array($datas);

echo var_dump($task);
$num = $task["num"];
$num = $num + 1;

echo "num now:" . $num . "\n";

while (1) {
$query = "INSERT INTO number (num) VALUES (" . $num . ")";
if (mysqli_query($dbc, $query)) {
echo date('Y-m-d H:i:s') . " : " . $query . "\n";
$num++;
} else {
echo mysqli_error($dbc) . "\n";
while (!($dbc = mysqli_connect(DB_HOST, DB_USER, DB_PASS, DB_NAME))) {
echo date('Y-m-d H:i:s') . " : sleep 1s" . "\n";
sleep(1);
}
mysqli_query($dbc, "SET NAMES 'UTF8'");
sleep(1);
}
}

?>
[root@manager01 ~]# php write.php

启动masterha_manager
[root@manager01 ~]# nohup masterha_manager --conf=/etc/mha/app1.cnf 2>&1 &

[root@manager01 ~]# cat /var/log/masterha/app1/manager.log
Thu May 10 13:18:57 2018 - [info] MHA::MasterMonitor version 0.56.
Thu May 10 13:18:58 2018 - [info] GTID failover mode = 0
Thu May 10 13:18:58 2018 - [info] Dead Servers:
Thu May 10 13:18:58 2018 - [info] Alive Servers:
Thu May 10 13:18:58 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:18:58 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Thu May 10 13:18:58 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Thu May 10 13:18:58 2018 - [info] Alive Slaves:
Thu May 10 13:18:58 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:18:58 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:18:58 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:18:58 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:18:58 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:18:58 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:18:58 2018 - [info] Current Alive Master: 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:18:58 2018 - [info] Checking slave configurations..
Thu May 10 13:18:58 2018 - [info] Checking replication filtering settings..
Thu May 10 13:18:58 2018 - [info] binlog_do_db= , binlog_ignore_db= mysql
Thu May 10 13:18:58 2018 - [info] Replication filtering check ok.
Thu May 10 13:18:58 2018 - [info] GTID (with auto-pos) is not supported
Thu May 10 13:18:58 2018 - [info] Starting SSH connection tests..
Thu May 10 13:18:59 2018 - [info] All SSH connection tests passed successfully.
Thu May 10 13:18:59 2018 - [info] Checking MHA Node version..
Thu May 10 13:19:00 2018 - [info] Version check ok.
Thu May 10 13:19:00 2018 - [info] Checking SSH publickey authentication settings on the current master..
Thu May 10 13:19:00 2018 - [info] HealthCheck: SSH to 10.78.72.73 is reachable.
Thu May 10 13:19:00 2018 - [info] Master MHA Node version is 0.56.
Thu May 10 13:19:00 2018 - [info] Checking recovery script configurations on 10.78.72.73(10.78.72.73:3306)..
Thu May 10 13:19:00 2018 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --start_file=mysql-bin.000005
Thu May 10 13:19:00 2018 - [info] Connecting to [email protected](10.78.72.73: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.000005
Thu May 10 13:19:00 2018 - [info] Binlog setting check done.
Thu May 10 13:19:00 2018 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Thu May 10 13:19:00 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha_rep' --slave_host=10.78.72.74 --slave_ip=10.78.72.74 --slave_port=3306 --workdir=/var/tmp --target_version=5.1.71-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Thu May 10 13:19:00 2018 - [info] Connecting to [email protected](10.78.72.74: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.000003
Temporary relay log file is /var/lib/mysql/relay-bin.000003
Testing mysql connection and privileges.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Thu May 10 13:19:00 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha_rep' --slave_host=10.78.72.75 --slave_ip=10.78.72.75 --slave_port=3306 --workdir=/var/tmp --target_version=5.1.71-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Thu May 10 13:19:00 2018 - [info] Connecting to [email protected](10.78.72.75: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.000003
Temporary relay log file is /var/lib/mysql/relay-bin.000003
Testing mysql connection and privileges.. done.
Testing mysqlbinlog output.. done.
Cleaning up test file(s).. done.
Thu May 10 13:19:01 2018 - [info] Slaves settings check done.
Thu May 10 13:19:01 2018 - [info]
10.78.72.73(10.78.72.73:3306) (current master)
+--10.78.72.74(10.78.72.74:3306)
+--10.78.72.75(10.78.72.75:3306)

Thu May 10 13:19:01 2018 - [info] Checking master_ip_failover_script status:
Thu May 10 13:19:01 2018 - [info] /etc/mha/scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=10.78.72.73 --orig_master_ip=10.78.72.73 --orig_master_port=3306


IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 10.78.72.77===

Checking the Status of the script.. OK
Thu May 10 13:19:01 2018 - [info] OK.
Thu May 10 13:19:01 2018 - [warning] shutdown_script is not defined.
Thu May 10 13:19:01 2018 - [info] Set master ping interval 1 seconds.
Thu May 10 13:19:01 2018 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Thu May 10 13:19:01 2018 - [info] Starting ping health check on 10.78.72.73(10.78.72.73:3306)..
Thu May 10 13:19:01 2018 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
[root@manager01 ~]#

手动关闭mysql或重启mysql服务器
1. 关闭原master 服务器
[root@manager01 ~]# tail -f /var/log/masterha/app1/manager.log
Thu May 10 13:42:15 2018 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)
Thu May 10 13:42:15 2018 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --binlog_prefix=mysql-bin
Thu May 10 13:42:15 2018 - [warning] HealthCheck: SSH to 10.78.72.73 is NOT reachable.
Thu May 10 13:42:16 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.73' (111))
Thu May 10 13:42:16 2018 - [warning] Connection failed 2 time(s)..
Thu May 10 13:42:17 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.73' (111))
Thu May 10 13:42:17 2018 - [warning] Connection failed 3 time(s)..
Thu May 10 13:42:18 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.73' (111))
Thu May 10 13:42:18 2018 - [warning] Connection failed 4 time(s)..
Thu May 10 13:42:18 2018 - [warning] Master is not reachable from health checker!
Thu May 10 13:42:18 2018 - [warning] Master 10.78.72.73(10.78.72.73:3306) is not reachable!
Thu May 10 13:42:18 2018 - [warning] SSH is NOT reachable.
Thu May 10 13:42:18 2018 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha/app1.cnf again, and trying to connect to all servers to check server status..
Thu May 10 13:42:18 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu May 10 13:42:18 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Thu May 10 13:42:18 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..
Thu May 10 13:42:19 2018 - [info] GTID failover mode = 0
Thu May 10 13:42:19 2018 - [info] Dead Servers:
Thu May 10 13:42:19 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:19 2018 - [info] Alive Servers:
Thu May 10 13:42:19 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Thu May 10 13:42:19 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Thu May 10 13:42:19 2018 - [info] Alive Slaves:
Thu May 10 13:42:19 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:19 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:19 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:42:19 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:19 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:19 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:42:19 2018 - [info] Checking slave configurations..
Thu May 10 13:42:19 2018 - [info] Checking replication filtering settings..
Thu May 10 13:42:19 2018 - [info] Replication filtering check ok.
Thu May 10 13:42:19 2018 - [info] Master is down!
Thu May 10 13:42:19 2018 - [info] Terminating monitoring script.
Thu May 10 13:42:19 2018 - [info] Got exit code 20 (Master dead).
Thu May 10 13:42:19 2018 - [info] MHA::MasterFailover version 0.56.
Thu May 10 13:42:19 2018 - [info] Starting master failover.
Thu May 10 13:42:19 2018 - [info]
Thu May 10 13:42:19 2018 - [info] * Phase 1: Configuration Check Phase..
Thu May 10 13:42:19 2018 - [info]
Thu May 10 13:42:20 2018 - [info] GTID failover mode = 0
Thu May 10 13:42:20 2018 - [info] Dead Servers:
Thu May 10 13:42:20 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Checking master reachability via MySQL(double check)...
Thu May 10 13:42:20 2018 - [info] ok.
Thu May 10 13:42:20 2018 - [info] Alive Servers:
Thu May 10 13:42:20 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Thu May 10 13:42:20 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Thu May 10 13:42:20 2018 - [info] Alive Slaves:
Thu May 10 13:42:20 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:42:20 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:42:20 2018 - [info] Starting Non-GTID based failover.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] ** Phase 1: Configuration Check Phase completed.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 2: Dead Master Shutdown Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] Forcing shutdown so that applications never connect to the current master..
Thu May 10 13:42:20 2018 - [info] Executing master IP deactivation script:
Thu May 10 13:42:20 2018 - [info] /etc/mha/scripts/master_ip_failover --orig_master_host=10.78.72.73 --orig_master_ip=10.78.72.73 --orig_master_port=3306 --command=stop


IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 10.78.72.77===

Disabling the VIP on old master: 10.78.72.73
Thu May 10 13:42:20 2018 - [info] done.
Thu May 10 13:42:20 2018 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Thu May 10 13:42:20 2018 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3: Master Recovery Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] The latest binary log file/position on all slaves is mysql-bin.000005:6369627
Thu May 10 13:42:20 2018 - [info] Latest slaves (Slaves that received relay log files to the latest):
Thu May 10 13:42:20 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:42:20 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:42:20 2018 - [info] The oldest binary log file/position on all slaves is mysql-bin.000005:6369627
Thu May 10 13:42:20 2018 - [info] Oldest slaves:
Thu May 10 13:42:20 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:42:20 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [warning] Dead Master is not SSH reachable. Could not save it's binlogs. Transactions that were not sent to the latest slave (Read_Master_Log_Pos to the tail of the dead master's binlog) were lost.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3.3: Determining New Master Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Thu May 10 13:42:20 2018 - [info] All slaves received relay logs to the same position. No need to resync each other.
Thu May 10 13:42:20 2018 - [info] Searching new master from slaves..
Thu May 10 13:42:20 2018 - [info] Candidate masters from the configuration file:
Thu May 10 13:42:20 2018 - [info] 10.78.72.74(10.78.72.74:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 13:42:20 2018 - [info] Non-candidate masters:
Thu May 10 13:42:20 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 13:42:20 2018 - [info] Replicating from 10.78.72.73(10.78.72.73:3306)
Thu May 10 13:42:20 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 13:42:20 2018 - [info] Searching from candidate_master slaves which have received the latest relay log events..
Thu May 10 13:42:20 2018 - [info] New master is 10.78.72.74(10.78.72.74:3306)
Thu May 10 13:42:20 2018 - [info] Starting master failover..
Thu May 10 13:42:20 2018 - [info]
From:
10.78.72.73(10.78.72.73:3306) (current master)
+--10.78.72.74(10.78.72.74:3306)
+--10.78.72.75(10.78.72.75:3306)

To:
10.78.72.74(10.78.72.74:3306) (new master)
+--10.78.72.75(10.78.72.75:3306)
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 3.4: Master Log Apply Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Thu May 10 13:42:20 2018 - [info] Starting recovery on 10.78.72.74(10.78.72.74:3306)..
Thu May 10 13:42:20 2018 - [info] This server has all relay logs. Waiting all logs to be applied..
Thu May 10 13:42:20 2018 - [info] done.
Thu May 10 13:42:20 2018 - [info] All relay logs were successfully applied.
Thu May 10 13:42:20 2018 - [info] Getting new master's binlog name and position..
Thu May 10 13:42:20 2018 - [info] mysql-bin.000004:6368065
Thu May 10 13:42:20 2018 - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='10.78.72.74', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000004', MASTER_LOG_POS=6368065, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Thu May 10 13:42:20 2018 - [info] Executing master IP activate script:
Thu May 10 13:42:20 2018 - [info] /etc/mha/scripts/master_ip_failover --command=start --ssh_user=root --orig_master_host=10.78.72.73 --orig_master_ip=10.78.72.73 --orig_master_port=3306 --new_master_host=10.78.72.74 --new_master_ip=10.78.72.74 --new_master_port=3306 --new_master_user='mha_rep' --new_master_password='Videobase.cn'
Unknown option: new_master_user
Unknown option: new_master_password


IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 10.78.72.77===

Enabling the VIP - 10.78.72.77 on the new master - 10.78.72.74
Thu May 10 13:42:20 2018 - [info] OK.
Thu May 10 13:42:20 2018 - [info] Setting read_only=0 on 10.78.72.74(10.78.72.74:3306)..
Thu May 10 13:42:20 2018 - [info] ok.
Thu May 10 13:42:20 2018 - [info] ** Finished master recovery successfully.
Thu May 10 13:42:20 2018 - [info] * Phase 3: Master Recovery Phase completed.
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 4: Slaves Recovery Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Thu May 10 13:42:20 2018 - [info]
Thu May 10 13:42:20 2018 - [info] -- Slave diff file generation on host 10.78.72.75(10.78.72.75:3306) started, pid: 4037. Check tmp log /var/log/masterha/app1/10.78.72.75_3306_20180510134219.log if it takes time..
Thu May 10 13:42:21 2018 - [info]
Thu May 10 13:42:21 2018 - [info] Log messages from 10.78.72.75 ...
Thu May 10 13:42:21 2018 - [info]
Thu May 10 13:42:20 2018 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu May 10 13:42:21 2018 - [info] End of log messages from 10.78.72.75.
Thu May 10 13:42:21 2018 - [info] -- 10.78.72.75(10.78.72.75:3306) has the latest relay log events.
Thu May 10 13:42:21 2018 - [info] Generating relay diff files from the latest slave succeeded.
Thu May 10 13:42:21 2018 - [info]
Thu May 10 13:42:21 2018 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Thu May 10 13:42:21 2018 - [info]
Thu May 10 13:42:21 2018 - [info] -- Slave recovery on host 10.78.72.75(10.78.72.75:3306) started, pid: 4039. Check tmp log /var/log/masterha/app1/10.78.72.75_3306_20180510134219.log if it takes time..
Thu May 10 13:42:22 2018 - [info]
Thu May 10 13:42:22 2018 - [info] Log messages from 10.78.72.75 ...
Thu May 10 13:42:22 2018 - [info]
Thu May 10 13:42:21 2018 - [info] Starting recovery on 10.78.72.75(10.78.72.75:3306)..
Thu May 10 13:42:21 2018 - [info] This server has all relay logs. Waiting all logs to be applied..
Thu May 10 13:42:21 2018 - [info] done.
Thu May 10 13:42:21 2018 - [info] All relay logs were successfully applied.
Thu May 10 13:42:21 2018 - [info] Resetting slave 10.78.72.75(10.78.72.75:3306) and starting replication from the new master 10.78.72.74(10.78.72.74:3306)..
Thu May 10 13:42:21 2018 - [info] Executed CHANGE MASTER.
Thu May 10 13:42:21 2018 - [info] Slave started.
Thu May 10 13:42:22 2018 - [info] End of log messages from 10.78.72.75.
Thu May 10 13:42:22 2018 - [info] -- Slave recovery on host 10.78.72.75(10.78.72.75:3306) succeeded.
Thu May 10 13:42:22 2018 - [info] All new slave servers recovered successfully.
Thu May 10 13:42:22 2018 - [info]
Thu May 10 13:42:22 2018 - [info] * Phase 5: New master cleanup phase..
Thu May 10 13:42:22 2018 - [info]
Thu May 10 13:42:22 2018 - [info] Resetting slave info on the new master..
Thu May 10 13:42:22 2018 - [info] 10.78.72.74: Resetting slave info succeeded.
Thu May 10 13:42:22 2018 - [info] Master failover to 10.78.72.74(10.78.72.74:3306) completed successfully.
Thu May 10 13:42:22 2018 - [info]

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

app1: MySQL Master failover 10.78.72.73(10.78.72.73:3306) to 10.78.72.74(10.78.72.74:3306) succeeded

Master 10.78.72.73(10.78.72.73:3306) is down!

Check MHA Manager logs at manager01:/var/log/masterha/app1/manager.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 10.78.72.73(10.78.72.73:3306)
The latest slave 10.78.72.74(10.78.72.74:3306) has all relay logs for recovery.
Selected 10.78.72.74(10.78.72.74:3306) as a new master.
10.78.72.74(10.78.72.74:3306): OK: Applying all logs succeeded.
10.78.72.74(10.78.72.74:3306): OK: Activated master IP address.
10.78.72.75(10.78.72.75:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
10.78.72.75(10.78.72.75:3306): OK: Applying all logs succeeded. Slave started, replicating from 10.78.72.74(10.78.72.74:3306)
10.78.72.74(10.78.72.74:3306): Resetting slave info succeeded.
Master failover to 10.78.72.74(10.78.72.74:3306) completed successfully.

# 删除failover.complete文件
[root@manager01 ~]# rm /var/log/masterha/app1/app1.failover.complete -f
# 启动masterha_manager
[root@manager01 ~]# nohup masterha_manager --conf=/etc/mha/app1.cnf 2>&1 &

# 恢复数据库参见 恢复故障
2. 关闭原master 服务
[root@manager01 ~]# tail -f /var/log/masterha/app1/manager.log
Thu May 10 18:21:20 2018 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)
Thu May 10 18:21:20 2018 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/tmp/save_binary_logs_test --manager_version=0.56 --binlog_prefix=mysql-bin
Thu May 10 18:21:20 2018 - [info] HealthCheck: SSH to 10.78.72.74 is reachable.
Thu May 10 18:21:21 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.74' (111))
Thu May 10 18:21:21 2018 - [warning] Connection failed 2 time(s)..
Thu May 10 18:21:22 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.74' (111))
Thu May 10 18:21:22 2018 - [warning] Connection failed 3 time(s)..
Thu May 10 18:21:23 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '10.78.72.74' (111))
Thu May 10 18:21:23 2018 - [warning] Connection failed 4 time(s)..
Thu May 10 18:21:23 2018 - [warning] Master is not reachable from health checker!
Thu May 10 18:21:23 2018 - [warning] Master 10.78.72.74(10.78.72.74:3306) is not reachable!
Thu May 10 18:21:23 2018 - [warning] SSH is reachable.
Thu May 10 18:21:23 2018 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha/app1.cnf again, and trying to connect to all servers to check server status..
Thu May 10 18:21:23 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu May 10 18:21:23 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Thu May 10 18:21:23 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..
Thu May 10 18:21:24 2018 - [info] GTID failover mode = 0
Thu May 10 18:21:24 2018 - [info] Dead Servers:
Thu May 10 18:21:24 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:24 2018 - [info] Alive Servers:
Thu May 10 18:21:24 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Thu May 10 18:21:24 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Thu May 10 18:21:24 2018 - [info] Alive Slaves:
Thu May 10 18:21:24 2018 - [info] 10.78.72.73(10.78.72.73:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:24 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:24 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 18:21:24 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:24 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:24 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 18:21:24 2018 - [info] Checking slave configurations..
Thu May 10 18:21:24 2018 - [info] Checking replication filtering settings..
Thu May 10 18:21:24 2018 - [info] Replication filtering check ok.
Thu May 10 18:21:24 2018 - [info] Master is down!
Thu May 10 18:21:24 2018 - [info] Terminating monitoring script.
Thu May 10 18:21:24 2018 - [info] Got exit code 20 (Master dead).
Thu May 10 18:21:24 2018 - [info] MHA::MasterFailover version 0.56.
Thu May 10 18:21:24 2018 - [info] Starting master failover.
Thu May 10 18:21:24 2018 - [info]
Thu May 10 18:21:24 2018 - [info] * Phase 1: Configuration Check Phase..
Thu May 10 18:21:24 2018 - [info]
Thu May 10 18:21:25 2018 - [info] GTID failover mode = 0
Thu May 10 18:21:25 2018 - [info] Dead Servers:
Thu May 10 18:21:25 2018 - [info] 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Checking master reachability via MySQL(double check)...
Thu May 10 18:21:25 2018 - [info] ok.
Thu May 10 18:21:25 2018 - [info] Alive Servers:
Thu May 10 18:21:25 2018 - [info] 10.78.72.73(10.78.72.73:3306)
Thu May 10 18:21:25 2018 - [info] 10.78.72.75(10.78.72.75:3306)
Thu May 10 18:21:25 2018 - [info] Alive Slaves:
Thu May 10 18:21:25 2018 - [info] 10.78.72.73(10.78.72.73:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 18:21:25 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 18:21:25 2018 - [info] Starting Non-GTID based failover.
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] ** Phase 1: Configuration Check Phase completed.
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] * Phase 2: Dead Master Shutdown Phase..
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] Forcing shutdown so that applications never connect to the current master..
Thu May 10 18:21:25 2018 - [info] Executing master IP deactivation script:
Thu May 10 18:21:25 2018 - [info] /etc/mha/scripts/master_ip_failover --orig_master_host=10.78.72.74 --orig_master_ip=10.78.72.74 --orig_master_port=3306 --command=stopssh --ssh_user=root


IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 10.78.72.77===

Disabling the VIP on old master: 10.78.72.74
Thu May 10 18:21:25 2018 - [info] done.
Thu May 10 18:21:25 2018 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Thu May 10 18:21:25 2018 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] * Phase 3: Master Recovery Phase..
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] The latest binary log file/position on all slaves is mysql-bin.000002:5344542
Thu May 10 18:21:25 2018 - [info] Latest slaves (Slaves that received relay log files to the latest):
Thu May 10 18:21:25 2018 - [info] 10.78.72.73(10.78.72.73:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 18:21:25 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 18:21:25 2018 - [info] The oldest binary log file/position on all slaves is mysql-bin.000002:5344542
Thu May 10 18:21:25 2018 - [info] Oldest slaves:
Thu May 10 18:21:25 2018 - [info] 10.78.72.73(10.78.72.73:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 18:21:25 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:25 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:25 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Thu May 10 18:21:25 2018 - [info]
Thu May 10 18:21:25 2018 - [info] Fetching dead master's binary logs..
Thu May 10 18:21:25 2018 - [info] Executing command on the dead master 10.78.72.74(10.78.72.74:3306): save_binary_logs --command=save --start_file=mysql-bin.000002 --start_pos=5344542 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.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.000002 pos 5344542 to mysql-bin.000002 EOF into /var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog ..
Dumping binlog format description event, from position 0 to 106.. ok.
Dumping effective binlog data from /var/lib/mysql/mysql-bin.000002 position 5344542 to tail(5344561).. ok.
Concat succeeded.
Thu May 10 18:21:25 2018 - [info] scp from [email protected]:/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog to local:/var/log/masterha/app1/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog succeeded.
Thu May 10 18:21:26 2018 - [info] HealthCheck: SSH to 10.78.72.73 is reachable.
Thu May 10 18:21:26 2018 - [info] HealthCheck: SSH to 10.78.72.75 is reachable.
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] * Phase 3.3: Determining New Master Phase..
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Thu May 10 18:21:26 2018 - [info] All slaves received relay logs to the same position. No need to resync each other.
Thu May 10 18:21:26 2018 - [info] Searching new master from slaves..
Thu May 10 18:21:26 2018 - [info] Candidate masters from the configuration file:
Thu May 10 18:21:26 2018 - [info] 10.78.72.73(10.78.72.73:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:26 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:26 2018 - [info] Primary candidate for the new Master (candidate_master is set)
Thu May 10 18:21:26 2018 - [info] Non-candidate masters:
Thu May 10 18:21:26 2018 - [info] 10.78.72.75(10.78.72.75:3306) Version=5.1.71-log (oldest major version between slaves) log-bin:enabled
Thu May 10 18:21:26 2018 - [info] Replicating from 10.78.72.74(10.78.72.74:3306)
Thu May 10 18:21:26 2018 - [info] Not candidate for the new Master (no_master is set)
Thu May 10 18:21:26 2018 - [info] Searching from candidate_master slaves which have received the latest relay log events..
Thu May 10 18:21:26 2018 - [info] New master is 10.78.72.73(10.78.72.73:3306)
Thu May 10 18:21:26 2018 - [info] Starting master failover..
Thu May 10 18:21:26 2018 - [info]
From:
10.78.72.74(10.78.72.74:3306) (current master)
+--10.78.72.73(10.78.72.73:3306)
+--10.78.72.75(10.78.72.75:3306)

To:
10.78.72.73(10.78.72.73:3306) (new master)
+--10.78.72.75(10.78.72.75:3306)
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu May 10 18:21:26 2018 - [info] Sending binlog..
Thu May 10 18:21:26 2018 - [info] scp from local:/var/log/masterha/app1/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog to [email protected]:/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog succeeded.
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] * Phase 3.4: Master Log Apply Phase..
Thu May 10 18:21:26 2018 - [info]
Thu May 10 18:21:26 2018 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Thu May 10 18:21:26 2018 - [info] Starting recovery on 10.78.72.73(10.78.72.73:3306)..
Thu May 10 18:21:26 2018 - [info] Generating diffs succeeded.
Thu May 10 18:21:26 2018 - [info] Waiting until all relay logs are applied.
Thu May 10 18:21:26 2018 - [info] done.
Thu May 10 18:21:26 2018 - [info] Getting slave status..
Thu May 10 18:21:26 2018 - [info] This slave(10.78.72.73)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000002:5344542). No need to recover from Exec_Master_Log_Pos.
Thu May 10 18:21:26 2018 - [info] Connecting to the target slave host 10.78.72.73, running recover script..
Thu May 10 18:21:26 2018 - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='mha_rep' --slave_host=10.78.72.73 --slave_ip=10.78.72.73 --slave_port=3306 --apply_files=/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog --workdir=/var/tmp --target_version=5.1.71-log --timestamp=20180510182124 --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56 --slave_pass=xxx
Thu May 10 18:21:27 2018 - [info]
Applying differential binary/relay log files /var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog on 10.78.72.73:3306. This may take long time...
Applying log files succeeded.
Thu May 10 18:21:27 2018 - [info] All relay logs were successfully applied.
Thu May 10 18:21:27 2018 - [info] Getting new master's binlog name and position..
Thu May 10 18:21:27 2018 - [info] mysql-bin.000002:106
Thu May 10 18:21:27 2018 - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='10.78.72.73', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=106, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Thu May 10 18:21:27 2018 - [info] Executing master IP activate script:
Thu May 10 18:21:27 2018 - [info] /etc/mha/scripts/master_ip_failover --command=start --ssh_user=root --orig_master_host=10.78.72.74 --orig_master_ip=10.78.72.74 --orig_master_port=3306 --new_master_host=10.78.72.73 --new_master_ip=10.78.72.73 --new_master_port=3306 --new_master_user='mha_rep' --new_master_password='Videobase.cn'
Unknown option: new_master_user
Unknown option: new_master_password


IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 10.78.72.77===

Enabling the VIP - 10.78.72.77 on the new master - 10.78.72.73
Thu May 10 18:21:27 2018 - [info] OK.
Thu May 10 18:21:27 2018 - [info] Setting read_only=0 on 10.78.72.73(10.78.72.73:3306)..
Thu May 10 18:21:27 2018 - [info] ok.
Thu May 10 18:21:27 2018 - [info] ** Finished master recovery successfully.
Thu May 10 18:21:27 2018 - [info] * Phase 3: Master Recovery Phase completed.
Thu May 10 18:21:27 2018 - [info]
Thu May 10 18:21:27 2018 - [info] * Phase 4: Slaves Recovery Phase..
Thu May 10 18:21:27 2018 - [info]
Thu May 10 18:21:27 2018 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Thu May 10 18:21:27 2018 - [info]
Thu May 10 18:21:27 2018 - [info] -- Slave diff file generation on host 10.78.72.75(10.78.72.75:3306) started, pid: 25781. Check tmp log /var/log/masterha/app1/10.78.72.75_3306_20180510182124.log if it takes time..
Thu May 10 18:21:28 2018 - [info]
Thu May 10 18:21:28 2018 - [info] Log messages from 10.78.72.75 ...
Thu May 10 18:21:28 2018 - [info]
Thu May 10 18:21:27 2018 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu May 10 18:21:28 2018 - [info] End of log messages from 10.78.72.75.
Thu May 10 18:21:28 2018 - [info] -- 10.78.72.75(10.78.72.75:3306) has the latest relay log events.
Thu May 10 18:21:28 2018 - [info] Generating relay diff files from the latest slave succeeded.
Thu May 10 18:21:28 2018 - [info]
Thu May 10 18:21:28 2018 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Thu May 10 18:21:28 2018 - [info]
Thu May 10 18:21:28 2018 - [info] -- Slave recovery on host 10.78.72.75(10.78.72.75:3306) started, pid: 25788. Check tmp log /var/log/masterha/app1/10.78.72.75_3306_20180510182124.log if it takes time..
Thu May 10 18:21:29 2018 - [info]
Thu May 10 18:21:29 2018 - [info] Log messages from 10.78.72.75 ...
Thu May 10 18:21:29 2018 - [info]
Thu May 10 18:21:28 2018 - [info] Sending binlog..
Thu May 10 18:21:28 2018 - [info] scp from local:/var/log/masterha/app1/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog to [email protected]:/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog succeeded.
Thu May 10 18:21:28 2018 - [info] Starting recovery on 10.78.72.75(10.78.72.75:3306)..
Thu May 10 18:21:28 2018 - [info] Generating diffs succeeded.
Thu May 10 18:21:28 2018 - [info] Waiting until all relay logs are applied.
Thu May 10 18:21:28 2018 - [info] done.
Thu May 10 18:21:28 2018 - [info] Getting slave status..
Thu May 10 18:21:28 2018 - [info] This slave(10.78.72.75)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000002:5344542). No need to recover from Exec_Master_Log_Pos.
Thu May 10 18:21:28 2018 - [info] Connecting to the target slave host 10.78.72.75, running recover script..
Thu May 10 18:21:28 2018 - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='mha_rep' --slave_host=10.78.72.75 --slave_ip=10.78.72.75 --slave_port=3306 --apply_files=/var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog --workdir=/var/tmp --target_version=5.1.71-log --timestamp=20180510182124 --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56 --slave_pass=xxx
Thu May 10 18:21:28 2018 - [info]
Applying differential binary/relay log files /var/tmp/saved_master_binlog_from_10.78.72.74_3306_20180510182124.binlog on 10.78.72.75:3306. This may take long time...
Applying log files succeeded.
Thu May 10 18:21:28 2018 - [info] All relay logs were successfully applied.
Thu May 10 18:21:28 2018 - [info] Resetting slave 10.78.72.75(10.78.72.75:3306) and starting replication from the new master 10.78.72.73(10.78.72.73:3306)..
Thu May 10 18:21:28 2018 - [info] Executed CHANGE MASTER.
Thu May 10 18:21:28 2018 - [info] Slave started.
Thu May 10 18:21:29 2018 - [info] End of log messages from 10.78.72.75.
Thu May 10 18:21:29 2018 - [info] -- Slave recovery on host 10.78.72.75(10.78.72.75:3306) succeeded.
Thu May 10 18:21:29 2018 - [info] All new slave servers recovered successfully.
Thu May 10 18:21:29 2018 - [info]
Thu May 10 18:21:29 2018 - [info] * Phase 5: New master cleanup phase..
Thu May 10 18:21:29 2018 - [info]
Thu May 10 18:21:29 2018 - [info] Resetting slave info on the new master..
Thu May 10 18:21:29 2018 - [info] 10.78.72.73: Resetting slave info succeeded.
Thu May 10 18:21:29 2018 - [info] Master failover to 10.78.72.73(10.78.72.73:3306) completed successfully.
Thu May 10 18:21:29 2018 - [info]

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

app1: MySQL Master failover 10.78.72.74(10.78.72.74:3306) to 10.78.72.73(10.78.72.73:3306) succeeded

Master 10.78.72.74(10.78.72.74:3306) is down!

Check MHA Manager logs at manager01:/var/log/masterha/app1/manager.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 10.78.72.74(10.78.72.74:3306)
The latest slave 10.78.72.73(10.78.72.73:3306) has all relay logs for recovery.
Selected 10.78.72.73(10.78.72.73:3306) as a new master.
10.78.72.73(10.78.72.73:3306): OK: Applying all logs succeeded.
10.78.72.73(10.78.72.73:3306): OK: Activated master IP address.
10.78.72.75(10.78.72.75:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
10.78.72.75(10.78.72.75:3306): OK: Applying all logs succeeded. Slave started, replicating from 10.78.72.73(10.78.72.73:3306)
10.78.72.73(10.78.72.73:3306): Resetting slave info succeeded.
Master failover to 10.78.72.73(10.78.72.73:3306) completed successfully.

# 删除failover.complete文件
[root@manager01 ~]# rm /var/log/masterha/app1/app1.failover.complete -f
# 启动masterha_manager
[root@manager01 ~]# nohup masterha_manager --conf=/etc/mha/app1.cnf 2>&1 &
# 恢复数据库参见 恢复故障

恢复故障

启动原master，手动切换到主库（恢复）

在原master上设置同步新master
mysql> reset master;
Query OK, 0 rows affected (0.04 sec)

# 从manager日志中查询change master to日志
# cat /var/log/masterha/app1/manager.log | grep "CHANGE MASTER"
mysql> CHANGE MASTER TO MASTER_HOST='10.78.72.73', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=106, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Query OK, 0 rows affected (0.08 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

mysql> show slave status \G

在原master上执行purge脚本（变成slave，需要执行purge，否则 [warning] relay_log_purge=0 is not set on slave ）
[root@mysql03 ~]# /usr/bin/purge_relay_logs --user=root --disable_relay_log_purge

删除failover文件
[root@manager01 ~]# rm /var/log/masterha/app1/app1.failover.complete -f

启动masterha_manager
[root@manager01 ~]# nohup masterha_manager --conf=/etc/mha/app1.cnf 2>&1 &

查看manager日志
[root@manager01 ~]# tail -f /var/log/masterha/app1/manager.log

增加keepalived

由于之前切换脚本直接通过远程执行 ifconfig eth0:1 添加子接口，会导致跨网段虚地址无法访问，需要通过vrrp协议的keepalive切换虚地址

编译安装keepalive

# 在master和slave-master上安装keepalive
yum -y install openssl-devel popt-devel libnl-devel
yum groupinstall "Development Tools" -y
ldconfig
tar xvf keepalived-1.2.7.tar.gz -C /usr/local/src/
cd /usr/local/src/keepalived-1.2.7/
./configure && make && make install
cp /usr/local/etc/rc.d/init.d/keepalived /etc/init.d/
cp /usr/local/etc/sysconfig/keepalived /etc/sysconfig/
mkdir /etc/keepalived
cp /usr/local/etc/keepalived/keepalived.conf /etc/keepalived/
cp /usr/local/sbin/keepalived /usr/sbin/

#配置文件
# master
[root@mysql01 ~]# cat /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
notification_email {
xxx
}
notification_email_from [email protected]
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id mysqlmha
}

vrrp_instance VI_1 {
# state为BACKUP，不是MASTER，避免抢占，从，还是按照原来的配置
state BACKUP
interface eth0
virtual_router_id 77
priority 100
advert_int 1
# 这个参数配置在主上，并且主state为BACKUP
nopreempt
authentication {
auth_type PASS
auth_pass formha
}
virtual_ipaddress {
10.78.72.77
}
}

# master-slave
! Configuration File for keepalived

global_defs {
notification_email {
xxx
}
notification_email_from [email protected]
smtp_server 127.0.0.1
smtp_connect_timeout 30
router_id mysqlmha
}

vrrp_instance VI_1 {
state BACKUP
interface eth0
virtual_router_id 77
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass formha
}
virtual_ipaddress {
10.78.72.77
}
}

# 在主上启动keepalive，不需要两个同时启动，在mha进行切换时会执行对应的启动或关闭keepalived


修改master_ip_failover脚本

[root@manager01 app1]# cat /etc/mha/scripts/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 = '10.78.72.77'; #vip地址
my $key = '1';
my $ssh_start_keepalived = "/etc/init.d/keepalived start";
my $ssh_stop_keepalived = "/etc/init.d/keepalived stop";
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 {
if ( $command eq "stop" || $command eq "stopssh" ) {
my $exit_code = 1;
eval {
print "Disabling the VIP on old master: $orig_master_host \n";
# stopssh命令才去执行stop vip
if ($command eq "stopssh") {
&stop_vip();
}
$exit_code = 0;
};
if ($@) {
warn "Got Error: $@\n";
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "start" ) {
my $exit_code = 10;
eval {
print "Enabling the VIP - $vip on the new master - $new_master_host \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";
exit 0;
}
else {
&usage();
exit 1;
}
}
sub start_vip() {
`ssh $ssh_user\@$new_master_host \" $ssh_start_keepalived \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`ssh $ssh_user\@$orig_master_host \" $ssh_stop_keepalived \"`;
}
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";
}

你可能感兴趣的:(数据库)

  • Google earth studio 简介 陟彼高冈yu 旅游
    GoogleEarthStudio是一个基于Web的动画工具，专为创作使用GoogleEarth数据的动画和视频而设计。它利用了GoogleEarth强大的三维地图和卫星影像数据库，使用户能够轻松地创建逼真的地球动画、航拍视频和动态地图可视化。网址为https://www.google.com/earth/studio/。GoogleEarthStudio是一个基于Web的动画工具，专为创作使用G
  • 关于提高复杂业务逻辑代码可读性的思考 编程经验分享 开发经验java数据库开发语言
    目录前言需求场景常规写法拆分方法领域对象总结前言实际工作中大部分时间都是在写业务逻辑，一般都是三层架构，表示层（Controller）接收客户端请求，并对入参做检验，业务逻辑层（Service）负责处理业务逻辑，一般开发都是在这一层中写具体的业务逻辑。数据访问层（Dao）是直接和数据库交互的，用于查数据给业务逻辑层，或者是将业务逻辑层处理后的数据写入数据库。简单的增删改查接口不用多说，基本上写好一
  • SQL Server_查询某一数据库中的所有表的内容 qq_42772833 SQLServer数据库sqlserver
    1.查看所有表的表名要列出CrabFarmDB数据库中的所有表（名），可以使用以下SQL语句：USECrabFarmDB;--切换到目标数据库GOSELECTTABLE_NAMEFROMINFORMATION_SCHEMA.TABLESWHERETABLE_TYPE='BASETABLE';对这段SQL脚本的解释：SELECTTABLE_NAME：这个语句的作用是从查询结果中选择TABLE_NAM
  • 深入理解 MultiQueryRetriever：提升向量数据库检索效果的强大工具 nseejrukjhad 数据库python
    深入理解MultiQueryRetriever：提升向量数据库检索效果的强大工具引言在人工智能和自然语言处理领域，高效准确的信息检索一直是一个关键挑战。传统的基于距离的向量数据库检索方法虽然广泛应用，但仍存在一些局限性。本文将介绍一种创新的解决方案：MultiQueryRetriever，它通过自动生成多个查询视角来增强检索效果，提高结果的相关性和多样性。MultiQueryRetriever的工
  • MongoDB Oplog 窗口 喝醉酒的小白 MongoDB运维
    在MongoDB中，oplog（操作日志）是一个特殊的日志系统，用于记录对数据库的所有写操作。oplog允许副本集成员（通常是从节点）应用主节点上已经执行的操作，从而保持数据的一致性。它是MongoDB副本集实现数据复制的基础。MongoDBOplog窗口oplog窗口是指在MongoDB副本集中，从节点可以用来同步数据的时间范围。这个窗口通常由以下因素决定：Oplog大小：oplog的大小是有限
  • python os 环境变量 CV矿工 python开发语言numpy
    环境变量：环境变量是程序和操作系统之间的通信方式。有些字符不宜明文写进代码里，比如数据库密码，个人账户密码，如果写进自己本机的环境变量里，程序用的时候通过os.environ.get（）取出来就行了。os.environ是一个环境变量的字典。环境变量的相关操作importos"""设置/修改环境变量：os.environ[‘环境变量名称’]=‘环境变量值’#其中key和value均为string类
  • 【PG】常见数据库、表属性设置 江无羡 数据库
    PG的常见属性配置方法数据库复制、备份相关表的复制标识单表操作批量表操作链接数据库复制、备份相关表的复制标识单表操作通过ALTER语句单独更改一张表的复制标识。ALTERTABLE[tablename]REPLICAIDENTITYFULL;批量表操作通过代码块的方式，对某个schema中的所有表一起更新其复制标识。SELECTtablename,CASErelreplidentWHEN'd'TH
  • nosql数据库技术与应用知识点 皆过客，揽星河 NoSQLnosql数据库大数据数据分析数据结构非关系型数据库
    Nosql知识回顾大数据处理流程数据采集(flume、爬虫、传感器)数据存储(本门课程NoSQL所处的阶段)Hdfs、MongoDB、HBase等数据清洗(入仓)Hive等数据处理、分析(Spark、Flink等)数据可视化数据挖掘、机器学习应用(Python、SparkMLlib等)大数据时代存储的挑战(三高)高并发(同一时间很多人访问)高扩展(要求随时根据需求扩展存储)高效率(要求读写速度快)
  • insert into select 主键自增_mybatis拦截器实现主键自动生成 weixin_39521651 insertintoselect主键自增mybatisdelete返回值mybatisinsert返回主键mybatisinsert返回对象mybatisplusinsert返回主键mybatisplus插入生成id
    前言前阵子和朋友聊天，他说他们项目有个需求，要实现主键自动生成，不想每次新增的时候，都手动设置主键。于是我就问他，那你们数据库表设置主键自动递增不就得了。他的回答是他们项目目前的id都是采用雪花算法来生成，因此为了项目稳定性，不会切换id的生成方式。朋友问我有没有什么实现思路，他们公司的orm框架是mybatis，我就建议他说，不然让你老大把mybatis切换成mybatis-plus。mybat
  • 关于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合理设置数据
  • Java爬虫框架（一）--架构设计 狼图腾-狼之传说 java框架java任务html解析器存储电子商务
    一、架构图那里搜网络爬虫框架主要针对电子商务网站进行数据爬取，分析，存储，索引。爬虫：爬虫负责爬取，解析，处理电子商务网站的网页的内容数据库：存储商品信息索引：商品的全文搜索索引Task队列：需要爬取的网页列表Visited表：已经爬取过的网页列表爬虫监控平台：web平台可以启动，停止爬虫，管理爬虫，task队列，visited表。二、爬虫1.流程1)Scheduler启动爬虫器，TaskMast
  • MongoDB知识概括 GeorgeLin98 持久层mongodb
    MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
  • Mongodb Error: queryTxt ETIMEOUT xxxx.wwwdz.mongodb.net 佛一脚 errorreactmongodb数据库
    背景每天都能遇到奇怪的问题，做个记录，以便有缘人能得到帮助！换了一台电脑开发nextjs程序。需要连接mongodb数据，对数据进行增删改查。上一台电脑好好的程序，新电脑死活连不上mongodb数据库。同一套代码，没任何修改，搞得我怀疑人生了，打开浏览器进入mongodb官网毫无问题，也能进入线上系统查看数据，网络应该是没问题。于是我尝试了一下手机热点，这次代码能正常跑起来，连接数据库了！！！是不
  • 入门MySQL——查询语法练习 K_un
    前言：前面几篇文章为大家介绍了DML以及DDL语句的使用方法，本篇文章将主要讲述常用的查询语法。其实MySQL官网给出了多个示例数据库供大家实用查询，下面我们以最常用的员工示例数据库为准，详细介绍各自常用的查询语法。1.员工示例数据库导入官方文档员工示例数据库介绍及下载链接：https://dev.mysql.com/doc/employee/en/employees-installation.h
  • 博客网站制作教程 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
  • 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
  • 【RabbitMQ 项目】服务端：数据管理模块之绑定管理 月夜星辉雪 rabbitmq分布式
    文章目录一.编写思路二.代码实践一.编写思路定义绑定信息类交换机名称队列名称绑定关键字：交换机的路由交换算法中会用到没有是否持久化的标志，因为绑定是否持久化取决于交换机和队列是否持久化，只有它们都持久化时绑定才需要持久化。绑定就好像一根绳子，两端连接着交换机和队列，当一方不存在，它就没有存在的必要了定义绑定持久化类构造函数：如果数据库文件不存在则创建，打开数据库，创建binding_table插入
  • 计算机毕业设计PHP仓储综合管理系统（源码+程序+VUE+lw+部署） java毕设程序源码王哥 php课程设计vue.js
    该项目含有源码、文档、程序、数据库、配套开发软件、软件安装教程。欢迎交流项目运行环境配置：phpStudy+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue+Express。项目技术：原生PHP++Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是小皮phpstudy最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
  • 3.增删改查--连接查询 问女何所忆
    关系型数据库的一个特点就是，多张表之间存在关系，以致于我们可以连接多张表进行查询操作，所以连接查询会是关系型数据库中最常见的操作。连接查询主要分为三种，交叉连接、内连接和外连接，我们一个个说。1、交叉连接交叉连接其实连接查询的第一个阶段，它简单表现为两张表的笛卡尔积形式，具体例子：如果你没学过数学中的笛卡尔积概念，你可以这样简单的理解这里的交叉连接：两张表的交叉连接就是一个连接合并的过程，T1表中
  • docker from指令的含义_多个FROM-含义 weixin_39722188 dockerfrom指令的含义
    小编典典什么是基本图片？一组文件，加上EXPOSE端口ENTRYPOINT和CMD。您可以添加文件并基于该基础图像构建新图像，Dockerfile并以FROM指令开头：后面提到的图像FROM是新图像的“基础图像”。这是否意味着如果我neo4j/neo4j在FROM指令中声明，则在运行映像时，neo数据库将自动运行并且可在端口7474的容器中使用？仅当您不覆盖CMD和时ENTRYPOINT。但是图像
  • Redis:缓存击穿 我的程序快快跑啊 缓存redisjava
    缓存击穿(热点key)：部分key(被高并发访问且缓存重建业务复杂的)失效,无数请求会直接到数据库，造成巨大压力1.互斥锁：可以保证强一致性线程一：未命中之后，获取互斥锁，再查询数据库重建缓存，写入缓存，释放锁线程二：查询未命中，未获得锁(已由线程一获得)，等待一会，缓存命中互斥锁实现方式：redis中setnxkeyvalue:改变对应key的value,仅当value不存在时执行，以此来实现互
  • 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
  • ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your †徐先森® Oracle数据库Web相关错误集
    createtablestudents(idintunsignedprimarykeyauto_increment,namevarchar(50)notnull,ageintunsigned,highdecimal(3,2),genderenum('男','女','中性','保密','妖')default'保密',cls_idintunsigned);在对数据库插入如上带有中文带有默认值的字段的时
  • Redis 有哪些危险命令？如何防范？ 花小疯 redis缓存数据库危险命令大数据
    Redis有哪些危险命令？Redis的危险命令主要有以下几个：1.keys客户端可查询出所有存在的键。2.flushdb删除Redis中当前所在数据库中的所有记录，并且此命令从不会执行失败。3.flushall删除Redis中所有数据库中的所有记录，不止是当前所在数据库，并且此命令从不会执行失败。4.config客户端可修改Redis配置。怎么禁用和重命名危险命令？看下redis.conf默认配置
  • 【Golang】 Golang 的 GORM 库中的 Rows 函数 不爱洗脚的小滕 golang开发语言后端
    文章目录前言一、Rows函数解释二、代码实现三、总结前言在使用Go语言进行数据库操作时，GORM（GoObject-RelationalMapping）库是一个常用的工具。它提供了一种简洁和强大的方式来处理数据库操作。本文将介绍GORM库中的Rows函数，这是一个用于执行原生SQL查询并返回结果的函数。一、Rows函数解释在GORM库中，Rows函数用于执行原生SQL查询并返回*sql.Rows结
  • 接口测试如何设计测试用例 李蕴Ronnie
    接口测试用例设计方式针对每个必填参数，都设计一条参数为空的测试用例必填参数不存在传的参数值在数据库中不存在添加数据接口，传入已有的数据重复添加编辑数据接口，各个字段分别编辑，合并编辑参数数据类型限制，针对每个参数设计一条参数值类型不符合的逆向用例参数自身取值范围，针对所有参数，设计一条每个参数值在取值范围内最大值的正向测试用例是否满足前提条件（token、headers），几个前提条件几条用例针对
  • Hadoop架构 henan程序媛 hadoop大数据分布式
    一、案列分析1.1案例概述现在已经进入了大数据(BigData)时代，数以万计用户的互联网服务时时刻刻都在产生大量的交互，要处理的数据量实在是太大了，以传统的数据库技术等其他手段根本无法应对数据处理的实时性、有效性的需求。HDFS顺应时代出现，在解决大数据存储和计算方面有很多的优势。1.2案列前置知识点1.什么是大数据大数据是指无法在一定时间范围内用常规软件工具进行捕捉、管理和处理的大量数据集合，
  • 非关系型数据库 天秤-white nosql
    一、为什么要用Nosql1.单机MySQL的时代。一个基本的网站访问量一般不会太大，单个数据库完全足够。那时候更多使用的静态网页html，服务器根本没有太大压力。这时候网站的瓶颈是什么？-数据量如果太大，一个机器放不下。-数据量太大需要建立数据的索引（B+Tree），一个服务器内存放不下。-访问量读写混合，一个服务器承受不了。2.memcached缓存+MySQL+垂直拆分（读写分离）。网站80%
  • 六、全局锁和表锁：给表加个字段怎么有这么多阻碍 nieniemin
    数据库锁设计的初衷是处理并发问题。作为多用户共享的资源，当出现并发访问的时候，数据库需要合理地控制资源的访问规则。而锁就是用来实现这些访问规则的重要数据结构。根据加锁的范围，MySQL里面的锁大致可以分成全局锁、表级锁和行锁三类。6.1全局锁全局锁就是对整个数据库实例加锁。MySQL提供了一个加全局读锁的方法，命令是Flushtableswithreadlock(FTWRL)。当你需要让整个库处于
  • 项目中 枚举与注解的结合使用 飞翔的马甲 javaenumannotation
    前言：版本兼容，一直是迭代开发头疼的事，最近新版本加上了支持新题型，如果新创建一份问卷包含了新题型，那旧版本客户端就不支持，如果新创建的问卷不包含新题型，那么新旧客户端都支持。这里面我们通过给问卷类型枚举增加自定义注解的方式完成。顺便巩固下枚举与注解。 一、枚举 1.在创建枚举类的时候，该类已继承java.lang.Enum类，所以自定义枚举类无法继承别的类，但可以实现接口。
  • 【Scala十七】Scala核心十一：下划线_的用法 bit1129 scala
    下划线_在Scala中广泛应用，_的基本含义是作为占位符使用。_在使用时是出问题非常多的地方，本文将不断完善_的使用场景以及所表达的含义   1. 在高阶函数中使用 scala> val list = List(-3,8,7,9) list: List[Int] = List(-3, 8, 7, 9) scala> list.filter(_ > 7) r
  • web缓存基础：术语、http报头和缓存策略 dalan_123 Web
    对于很多人来说，去访问某一个站点，若是该站点能够提供智能化的内容缓存来提高用户体验，那么最终该站点的访问者将络绎不绝。缓存或者对之前的请求临时存储，是http协议实现中最核心的内容分发策略之一。分发路径中的组件均可以缓存内容来加速后续的请求，这是受控于对该内容所声明的缓存策略。接下来将讨web内容缓存策略的基本概念，具体包括如如何选择缓存策略以保证互联网范围内的缓存能够正确处理的您的内容，并谈论下
  • crontab 问题 周凡杨 linuxcrontabunix
      一： 0481-079   Reached   a   symbol   that   is   not   expected.   背景： */5   *   *   *   *  /usr/IBMIHS/rsync.sh 
  • 让tomcat支持2级域名共享session g21121 session
    tomcat默认情况下是不支持2级域名共享session的，所有有些情况下登陆后从主域名跳转到子域名会发生链接session不相同的情况，但是只需修改几处配置就可以了。 打开tomcat下conf下context.xml文件 找到Context标签,修改为如下内容 如果你的域名是www.test.com <Context sessionCookiePath="/path&q
  • web报表工具FineReport常用函数的用法总结（数学和三角函数） 老A不折腾 Webfinereport总结
      ABS ABS(number):返回指定数字的绝对值。绝对值是指没有正负符号的数值。 Number:需要求出绝对值的任意实数。 示例: ABS(-1.5)等于1.5。 ABS(0)等于0。 ABS(2.5)等于2.5。   ACOS ACOS(number):返回指定数值的反余弦值。反余弦值为一个角度，返回角度以弧度形式表示。 Number:需要返回角
  • linux 启动java进程 sh文件 墙头上一根草 linuxshelljar
    #!/bin/bash #初始化服务器的进程PId变量 user_pid=0; robot_pid=0; loadlort_pid=0; gateway_pid=0; ######### #检查相关服务器是否启动成功 #说明： #使用JDK自带的JPS命令及grep命令组合，准确查找pid #jps 加 l 参数，表示显示java的完整包路径 #使用awk，分割出pid
  • 我的spring学习笔记5-如何使用ApplicationContext替换BeanFactory aijuans Spring 3 系列
    如何使用ApplicationContext替换BeanFactory？ package onlyfun.caterpillar.device; import org.springframework.beans.factory.BeanFactory; import org.springframework.beans.factory.xml.XmlBeanFactory; import
  • Linux 内存使用方法详细解析 annan211 linux内存Linux内存解析
    来源 http://blog.jobbole.com/45748/ 我是一名程序员，那么我在这里以一个程序员的角度来讲解Linux内存的使用。 一提到内存管理，我们头脑中闪出的两个概念，就是虚拟内存，与物理内存。这两个概念主要来自于linux内核的支持。 Linux在内存管理上份为两级，一级是线性区，类似于00c73000-00c88000，对应于虚拟内存，它实际上不占用
  • 数据库的单表查询常用命令及使用方法(-) 百合不是茶 oracle函数单表查询
        创建数据库;       --建表 create table bloguser(username varchar2(20),userage number(10),usersex char(2));       创建bloguser表,里面有三个字段     &nbs
  • 多线程基础知识 bijian1013 java多线程threadjava多线程
    一．进程和线程 进程就是一个在内存中独立运行的程序，有自己的地址空间。如正在运行的写字板程序就是一个进程。 “多任务”：指操作系统能同时运行多个进程（程序）。如WINDOWS系统可以同时运行写字板程序、画图程序、WORD、Eclipse等。 线程：是进程内部单一的一个顺序控制流。 线程和进程 a.       每个进程都有独立的
  • fastjson简单使用实例 bijian1013 fastjson
    一.简介         阿里巴巴fastjson是一个Java语言编写的高性能功能完善的JSON库。它采用一种“假定有序快速匹配”的算法，把JSON Parse的性能提升到极致，是目前Java语言中最快的JSON库；包括“序列化”和“反序列化”两部分，它具备如下特征：     
  • 【RPC框架Burlap】Spring集成Burlap bit1129 spring
    Burlap和Hessian同属于codehaus的RPC调用框架，但是Burlap已经几年不更新，所以Spring在4.0里已经将Burlap的支持置为Deprecated,所以在选择RPC框架时，不应该考虑Burlap了。 这篇文章还是记录下Burlap的用法吧，主要是复制粘贴了Hessian与Spring集成一文，【RPC框架Hessian四】Hessian与Spring集成  
  • 【Mahout一】基于Mahout 命令参数含义 bit1129 Mahout
    1. mahout seqdirectory   $ mahout seqdirectory --input (-i) input Path to job input directory(原始文本文件). --output (-o) output The directory pathna
  • linux使用flock文件锁解决脚本重复执行问题 ronin47 linux lock　重复执行
    linux的crontab命令，可以定时执行操作，最小周期是每分钟执行一次。关于crontab实现每秒执行可参考我之前的文章《linux crontab 实现每秒执行》现在有个问题，如果设定了任务每分钟执行一次，但有可能一分钟内任务并没有执行完成，这时系统会再执行任务。导致两个相同的任务在执行。 例如： <? //  test .php
  • java-74-数组中有一个数字出现的次数超过了数组长度的一半，找出这个数字 bylijinnan java
    public class OcuppyMoreThanHalf { /** * Q74 数组中有一个数字出现的次数超过了数组长度的一半，找出这个数字 * two solutions: * 1.O(n) * see <beauty of coding>--每次删除两个不同的数字，不改变数组的特性 * 2.O(nlogn) * 排序。中间
  • linux 系统相关命令 candiio linux
    系统参数 cat /proc/cpuinfo  cpu相关参数 cat /proc/meminfo 内存相关参数 cat /proc/loadavg 负载情况 性能参数 1）top M：按内存使用排序 P：按CPU占用排序 1：显示各CPU的使用情况 k：kill进程 o：更多排序规则 回车：刷新数据 2）ulimit ulimit -a：显示本用户的系统限制参
  • [经营与资产]保持独立性和稳定性对于软件开发的重要意义 comsci 软件开发
         一个软件的架构从诞生到成熟，中间要经过很多次的修正和改造       如果在这个过程中，外界的其它行业的资本不断的介入这种软件架构的升级过程中           那么软件开发者原有的设计思想和开发路线
  • 在CentOS5.5上编译OpenJDK6 Cwind linuxOpenJDK
    几番周折终于在自己的CentOS5.5上编译成功了OpenJDK6，将编译过程和遇到的问题作一简要记录，备查。 0. OpenJDK介绍 OpenJDK是Sun（现Oracle）公司发布的基于GPL许可的Java平台的实现。其优点： 1、它的核心代码与同时期Sun（-> Oracle）的产品版基本上是一样的，血统纯正，不用担心性能问题，也基本上没什么兼容性问题；（代码上最主要的差异是
  • java乱码问题 dashuaifu java乱码问题js中文乱码
    swfupload上传文件参数值为中文传递到后台接收中文乱码     在js中用setPostParams（{"tag" : encodeURI( document.getElementByIdx_x("filetag").value，"utf-8")}）; 然后在servlet中String t
  • cygwin很多命令显示command not found的解决办法 dcj3sjt126com cygwin
    cygwin很多命令显示command not found的解决办法   修改cygwin.BAT文件如下 @echo off D: set CYGWIN=tty notitle glob set PATH=%PATH%;d:\cygwin\bin;d:\cygwin\sbin;d:\cygwin\usr\bin;d:\cygwin\usr\sbin;d:\cygwin\us
  • [介绍]从 Yii 1.1 升级 dcj3sjt126com PHPyii2
    2.0 版框架是完全重写的，在 1.1 和 2.0 两个版本之间存在相当多差异。因此从 1.1 版升级并不像小版本间的跨越那么简单，通过本指南你将会了解两个版本间主要的不同之处。 如果你之前没有用过 Yii 1.1，可以跳过本章，直接从"入门篇"开始读起。 请注意，Yii 2.0 引入了很多本章并没有涉及到的新功能。强烈建议你通读整部权威指南来了解所有新特性。这样有可能会发
  • Linux SSH免登录配置总结 eksliang ssh-keygenLinux SSH免登录认证Linux SSH互信
    转载请出自出处：http://eksliang.iteye.com/blog/2187265 一、原理      我们使用ssh-keygen在ServerA上生成私钥跟公钥，将生成的公钥拷贝到远程机器ServerB上后,就可以使用ssh命令无需密码登录到另外一台机器ServerB上。      生成公钥与私钥有两种加密方式，第一种是
  • 手势滑动销毁Activity gundumw100 android
    老是效仿ios，做android的真悲催！ 有需求：需要手势滑动销毁一个Activity 怎么办尼？自己写？ 不用~，网上先问一下百度。 结果： http://blog.csdn.net/xiaanming/article/details/20934541 首先将你需要的Activity继承SwipeBackActivity，它会在你的布局根目录新增一层SwipeBackLay
  • JavaScript变换表格边框颜色 ini JavaScripthtmlWebhtml5css
    效果查看：http://hovertree.com/texiao/js/2.htm代码如下，保存到HTML文件也可以查看效果： <html> <head> <meta charset="utf-8"> <title>表格边框变换颜色代码-何问起</title> </head> <body&
  • Kafka Rest : Confluent kane_xie kafkaRESTconfluent
    最近拿到一个kafka rest的需求，但kafka暂时还没有提供rest api（应该是有在开发中，毕竟rest这么火），上网搜了一下，找到一个Confluent Platform，本文简单介绍一下安装。 这里插一句，给大家推荐一个九尾搜索，原名叫谷粉SOSO，不想fanqiang谷歌的可以用这个。以前在外企用谷歌用习惯了，出来之后用度娘搜技术问题，那匹配度简直感人。 环境声明：Ubu
  • Calender不是单例 men4661273 单例Calender
             在我们使用Calender的时候，使用过Calendar.getInstance()来获取一个日期类的对象，这种方式跟单例的获取方式一样，那么它到底是不是单例呢，如果是单例的话，一个对象修改内容之后，另外一个线程中的数据不久乱套了吗？从试验以及源码中可以得出，Calendar不是单例。 测试： Calendar c1 =
  • 线程内存和主内存之间联系 qifeifei java thread
    1， java多线程共享主内存中变量的时候，一共会经过几个阶段，    lock:将主内存中的变量锁定，为一个线程所独占。   unclock:将lock加的锁定解除，此时其它的线程可以有机会访问此变量。   read:将主内存中的变量值读到工作内存当中。   load:将read读取的值保存到工作内存中的变量副本中。  
  • schedule和scheduleAtFixedRate tangqi609567707 javatimerschedule
    原文地址：http://blog.csdn.net/weidan1121/article/details/527307 import java.util.Timer;import java.util.TimerTask;import java.util.Date; /** * @author vincent */public class TimerTest {  
  • erlang 部署 wudixiaotie erlang
    1.如果在启动节点的时候报这个错 ： {"init terminating in do_boot",{'cannot load',elf_format,get_files}} 则需要在reltool.config中加入 {app, hipe, [{incl_cond, exclude}]},     2.当generate时，遇到： ERROR
按字母分类： ABCDEFGHIJKLMNOPQRSTUVWXYZ其他