利用sysbench工具测试MHA

最新推荐文章于 2022-04-17 18:00:16 发布
最新推荐文章于 2022-04-17 18:00:16 发布
阅读量251 收藏
点赞数
文章标签： 运维 数据库 lua
原文链接：http://www.cnblogs.com/wanbin/p/9899596.html
版权

利用sysbench工具测试MHA

1. sysbench准备数据

sysbench /usr/share/sysbench/oltp_read_write.lua \
--mysql-host=192.168.56.111 \
--mysql-user=wanbin \
--mysql-password=mysql \
--mysql-db=sbtest \
--db-driver=mysql \
--tables=10 \
--table-size=500000 \
--report-interval=10 \
--threads=128 \
--time=120 \
prepare



prepare/run/cleanup
prepare:准备数据，
run：执行压测，
cleanup:清除数据

sysbench 1.0.15 (using bundled LuaJIT 2.1.0-beta2)

Initializing worker threads...

Creating table 'sbtest10'...
Creating table 'sbtest6'...
Creating table 'sbtest1'...
Creating table 'sbtest3'...
Creating table 'sbtest2'...
Creating table 'sbtest7'...
Creating table 'sbtest5'...
Creating table 'sbtest8'...
Creating table 'sbtest4'...
Creating table 'sbtest9'...
Inserting 500000 records into 'sbtest10'
Inserting 500000 records into 'sbtest9'
Inserting 500000 records into 'sbtest6'
Inserting 500000 records into 'sbtest5'
Inserting 500000 records into 'sbtest8'
Inserting 500000 records into 'sbtest4'
Inserting 500000 records into 'sbtest7'
Inserting 500000 records into 'sbtest3'
Inserting 500000 records into 'sbtest2'
Inserting 500000 records into 'sbtest1'
Creating a secondary index on 'sbtest5'...
Creating a secondary index on 'sbtest6'...
Creating a secondary index on 'sbtest9'...
Creating a secondary index on 'sbtest10'...
Creating a secondary index on 'sbtest7'...
Creating a secondary index on 'sbtest3'...
Creating a secondary index on 'sbtest8'...
Creating a secondary index on 'sbtest2'...
Creating a secondary index on 'sbtest4'...
Creating a secondary index on 'sbtest1'...

2. sysbench开始压测

sysbench /usr/share/sysbench/oltp_read_write.lua \
--mysql-host=192.168.56.111 \
--mysql-user=wanbin \
--mysql-password=mysql \
--mysql-db=sbtest \
--db-driver=mysql \
--tables=10 \
--table-size=500000 \
--report-interval=10 \
--threads=128 \
--time=120 \
run

3. master模拟意外宕机

# ps -ef|grep mysqld
avahi      741     1  0 08:50 ?        00:00:00 avahi-daemon: running [mysqldb1.local]
mysql     4741  4228  2 11:03 pts/3    00:06:30 mysqld --defaults-file=/etc/my3306.cnf
root      8346  8288  0 15:34 pts/0    00:00:00 grep --color=auto mysqld

# kill -9 4741

4. mysqldb2 上观察mha状态

# tail -f /var/log/masterha/app1/manager.log

Mon Oct 29 15:34:40 2018 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Mon Oct 29 15:34:40 2018 - [info] Executing secondary network check script: /usr/local/bin/masterha_secondary_check -s mysqldb2 -s mysqldb1  --user=root  --master_host=192.168.56.100  --master_ip=192.168.56.100  --master_port=3306 --master_user=mha_rep --master_password=123456 --ping_type=SELECT
Mon Oct 29 15:34:40 2018 - [info] Executing SSH check script: exit 0
Mon Oct 29 15:34:40 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.100' (111))
Mon Oct 29 15:34:40 2018 - [warning] Connection failed 2 time(s)..
Mon Oct 29 15:34:41 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.100' (111))
Mon Oct 29 15:34:41 2018 - [warning] Connection failed 3 time(s)..
Mon Oct 29 15:34:42 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.100' (111))
Mon Oct 29 15:34:42 2018 - [warning] Connection failed 4 time(s)..
Mon Oct 29 15:34:45 2018 - [warning] HealthCheck: Got timeout on checking SSH connection to 192.168.56.100! at /usr/local/share/perl5/MHA/HealthCheck.pm line 342.
Monitoring server mysqldb2 is reachable, Master is not reachable from mysqldb2. OK.
Monitoring server mysqldb1 is reachable, Master is not reachable from mysqldb1. OK.
Mon Oct 29 15:34:53 2018 - [info] Master is not reachable from all other monitoring servers. Failover should start.
Mon Oct 29 15:34:53 2018 - [warning] Master is not reachable from health checker!
Mon Oct 29 15:34:53 2018 - [warning] Master 192.168.56.100(192.168.56.100:3306) is not reachable!
Mon Oct 29 15:34:53 2018 - [warning] SSH is NOT reachable.
Mon Oct 29 15:34:53 2018 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..
Mon Oct 29 15:34:53 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon Oct 29 15:34:53 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:34:53 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:34:55 2018 - [info] GTID failover mode = 1
Mon Oct 29 15:34:55 2018 - [info] Dead Servers:
Mon Oct 29 15:34:55 2018 - [info]   192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:55 2018 - [info] Alive Servers:
Mon Oct 29 15:34:55 2018 - [info]   192.168.56.200(192.168.56.200:3306)
Mon Oct 29 15:34:55 2018 - [info]   192.168.56.210(192.168.56.210:3306)
Mon Oct 29 15:34:55 2018 - [info] Alive Slaves:
Mon Oct 29 15:34:55 2018 - [info]   192.168.56.200(192.168.56.200:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:34:55 2018 - [info]     GTID ON
Mon Oct 29 15:34:55 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:55 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Oct 29 15:34:55 2018 - [info]   192.168.56.210(192.168.56.210:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:34:55 2018 - [info]     GTID ON
Mon Oct 29 15:34:55 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:55 2018 - [info]     Not candidate for the new Master (no_master is set)
Mon Oct 29 15:34:55 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon Oct 29 15:34:55 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:34:55 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:34:55 2018 - [info] Checking slave configurations..
Mon Oct 29 15:34:55 2018 - [info] Checking replication filtering settings..
Mon Oct 29 15:34:55 2018 - [info]  Replication filtering check ok.
Mon Oct 29 15:34:55 2018 - [info] Master is down!
Mon Oct 29 15:34:55 2018 - [info] Terminating monitoring script.
Mon Oct 29 15:34:55 2018 - [info] Got exit code 20 (Master dead).
Mon Oct 29 15:34:55 2018 - [info] MHA::MasterFailover version 0.57.
Mon Oct 29 15:34:55 2018 - [info] Starting master failover.
Mon Oct 29 15:34:55 2018 - [info] 
Mon Oct 29 15:34:55 2018 - [info] * Phase 1: Configuration Check Phase..
Mon Oct 29 15:34:55 2018 - [info] 
Mon Oct 29 15:34:56 2018 - [info] GTID failover mode = 1
Mon Oct 29 15:34:56 2018 - [info] Dead Servers:
Mon Oct 29 15:34:56 2018 - [info]   192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:56 2018 - [info] Checking master reachability via MySQL(double check)...
Mon Oct 29 15:34:56 2018 - [info]  ok.
Mon Oct 29 15:34:56 2018 - [info] Alive Servers:
Mon Oct 29 15:34:56 2018 - [info]   192.168.56.200(192.168.56.200:3306)
Mon Oct 29 15:34:56 2018 - [info]   192.168.56.210(192.168.56.210:3306)
Mon Oct 29 15:34:56 2018 - [info] Alive Slaves:
Mon Oct 29 15:34:56 2018 - [info]   192.168.56.200(192.168.56.200:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:34:56 2018 - [info]     GTID ON
Mon Oct 29 15:34:56 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:56 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Oct 29 15:34:56 2018 - [info]   192.168.56.210(192.168.56.210:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:34:56 2018 - [info]     GTID ON
Mon Oct 29 15:34:56 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:34:56 2018 - [info]     Not candidate for the new Master (no_master is set)
Mon Oct 29 15:34:56 2018 - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln309] Last failover was done at 2018/10/29 10:09:03. Current time is too early to do failover again. If you want to do failover, manually remove /var/log/masterha/app1/app1.failover.complete and run this script again.
Mon Oct 29 15:34:56 2018 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR:  at /usr/local/bin/masterha_manager line 65.

可以看到自动切换失败，需要删除/var/log/masterha/app1/app1.failover.complete

rm -rf /var/log/masterha/app1/app1.failover.complete

5. 手工failover切换master

# masterha_master_switch --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.56.100 --master_state=dead --new_master_host=192.168.56.200 --ignore_last_failover

--ignore_last_failover：在缺省情况下，如果MHA检测到连续发生宕机，且两次宕机间隔不足8小时的话，
则不会进行Failover，之所以这样限制是为了避免ping-pong效应。
该参数代表忽略上次MHA触发切换产生的文件，默认情况下，MHA发生切换后会在日志目录，
也就是 /var/log/masterha/app1产生app1.failover.complete文件，
下次再次切换的时候如果发现该目录下存在该文件将不允许触发切换，除非在第一次切换后收到删除该文件

# masterha_master_switch --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.56.100 --master_state=dead --new_master_host=192.168.56.200 --ignore_last_failover
--dead_master_ip=<dead_master_ip> is not set. Using 192.168.56.100.
--dead_master_port=<dead_master_port> is not set. Using 3306.
Mon Oct 29 15:49:04 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon Oct 29 15:49:04 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:49:04 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Mon Oct 29 15:49:04 2018 - [info] MHA::MasterFailover version 0.57.
Mon Oct 29 15:49:04 2018 - [info] Starting master failover.
Mon Oct 29 15:49:04 2018 - [info] 
Mon Oct 29 15:49:04 2018 - [info] * Phase 1: Configuration Check Phase..
Mon Oct 29 15:49:04 2018 - [info] 
Mon Oct 29 15:49:05 2018 - [info] GTID failover mode = 1
Mon Oct 29 15:49:05 2018 - [info] Dead Servers:
Mon Oct 29 15:49:05 2018 - [info]   192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:05 2018 - [info] Checking master reachability via MySQL(double check)...
Mon Oct 29 15:49:05 2018 - [info]  ok.
Mon Oct 29 15:49:05 2018 - [info] Alive Servers:
Mon Oct 29 15:49:05 2018 - [info]   192.168.56.200(192.168.56.200:3306)
Mon Oct 29 15:49:05 2018 - [info]   192.168.56.210(192.168.56.210:3306)
Mon Oct 29 15:49:05 2018 - [info] Alive Slaves:
Mon Oct 29 15:49:05 2018 - [info]   192.168.56.200(192.168.56.200:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:05 2018 - [info]     GTID ON
Mon Oct 29 15:49:05 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:05 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Oct 29 15:49:05 2018 - [info]   192.168.56.210(192.168.56.210:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:05 2018 - [info]     GTID ON
Mon Oct 29 15:49:05 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:05 2018 - [info]     Not candidate for the new Master (no_master is set)
Master 192.168.56.100(192.168.56.100:3306) is dead. Proceed? (yes/NO): yes
Mon Oct 29 15:49:06 2018 - [info] Starting GTID based failover.
Mon Oct 29 15:49:06 2018 - [info] 
Mon Oct 29 15:49:06 2018 - [info] ** Phase 1: Configuration Check Phase completed.
Mon Oct 29 15:49:06 2018 - [info] 
Mon Oct 29 15:49:06 2018 - [info] * Phase 2: Dead Master Shutdown Phase..
Mon Oct 29 15:49:06 2018 - [info] 
Mon Oct 29 15:49:07 2018 - [info] HealthCheck: SSH to 192.168.56.100 is reachable.
Mon Oct 29 15:49:07 2018 - [info] Forcing shutdown so that applications never connect to the current master..
Mon Oct 29 15:49:07 2018 - [info] Executing master IP deactivation script:
Mon Oct 29 15:49:07 2018 - [info]   /usr/local/bin/master_ip_failover --orig_master_host=192.168.56.100 --orig_master_ip=192.168.56.100 --orig_master_port=3306 --command=stopssh --ssh_user=root  


IN SCRIPT TEST====/sbin/ifconfig eth0:0 down==/sbin/ifconfig eth0:0 192.168.56.111/24 up===

Disabling the VIP on old master: 192.168.56.100 
Mon Oct 29 15:49:08 2018 - [info]  done.
Mon Oct 29 15:49:08 2018 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Mon Oct 29 15:49:08 2018 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Mon Oct 29 15:49:08 2018 - [info] 
Mon Oct 29 15:49:08 2018 - [info] * Phase 3: Master Recovery Phase..
Mon Oct 29 15:49:08 2018 - [info] 
Mon Oct 29 15:49:08 2018 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Mon Oct 29 15:49:08 2018 - [info] 
Mon Oct 29 15:49:08 2018 - [info] The latest binary log file/position on all slaves is my3306_binlog.000027:860190114
Mon Oct 29 15:49:08 2018 - [info] Retrieved Gtid Set: 7390a401-b705-11e8-9ed9-080027b0b461:140923-149275
Mon Oct 29 15:49:08 2018 - [info] Latest slaves (Slaves that received relay log files to the latest):
Mon Oct 29 15:49:08 2018 - [info]   192.168.56.200(192.168.56.200:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:08 2018 - [info]     GTID ON
Mon Oct 29 15:49:08 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:08 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Oct 29 15:49:08 2018 - [info]   192.168.56.210(192.168.56.210:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:08 2018 - [info]     GTID ON
Mon Oct 29 15:49:08 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:08 2018 - [info]     Not candidate for the new Master (no_master is set)
Mon Oct 29 15:49:08 2018 - [info] The oldest binary log file/position on all slaves is my3306_binlog.000027:860190114
Mon Oct 29 15:49:08 2018 - [info] Retrieved Gtid Set: 7390a401-b705-11e8-9ed9-080027b0b461:140923-149275
Mon Oct 29 15:49:08 2018 - [info] Oldest slaves:
Mon Oct 29 15:49:08 2018 - [info]   192.168.56.200(192.168.56.200:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:08 2018 - [info]     GTID ON
Mon Oct 29 15:49:08 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:08 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Oct 29 15:49:08 2018 - [info]   192.168.56.210(192.168.56.210:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabled
Mon Oct 29 15:49:08 2018 - [info]     GTID ON
Mon Oct 29 15:49:08 2018 - [info]     Replicating from 192.168.56.100(192.168.56.100:3306)
Mon Oct 29 15:49:08 2018 - [info]     Not candidate for the new Master (no_master is set)
Mon Oct 29 15:49:08 2018 - [info] 
Mon Oct 29 15:49:08 2018 - [info] * Phase 3.3: Determining New Master Phase..
Mon Oct 29 15:49:08 2018 - [info] 
Mon Oct 29 15:49:08 2018 - [info] 192.168.56.200 can be new master.
Mon Oct 29 15:49:08 2018 - [info] New master is 192.168.56.200(192.168.56.200:3306)
Mon Oct 29 15:49:08 2018 - [info] Starting master failover..
Mon Oct 29 15:49:08 2018 - [info] 
From:
192.168.56.100(192.168.56.100:3306) (current master)
 +--192.168.56.200(192.168.56.200:3306)
 +--192.168.56.210(192.168.56.210:3306)

To:
192.168.56.200(192.168.56.200:3306) (new master)
 +--192.168.56.210(192.168.56.210:3306)

Starting master switch from 192.168.56.100(192.168.56.100:3306) to 192.168.56.200(192.168.56.200:3306)? (yes/NO): yes
Mon Oct 29 15:49:09 2018 - [info] New master decided manually is 192.168.56.200(192.168.56.200:3306)
Mon Oct 29 15:49:09 2018 - [info] 
Mon Oct 29 15:49:09 2018 - [info] * Phase 3.3: New Master Recovery Phase..
Mon Oct 29 15:49:09 2018 - [info] 
Mon Oct 29 15:49:09 2018 - [info]  Waiting all logs to be applied.. 
Mon Oct 29 15:49:09 2018 - [info]   done.
Mon Oct 29 15:49:09 2018 - [info] Getting new master's binlog name and position..
Mon Oct 29 15:49:09 2018 - [info]  my3306_binlog.000016:965341200
Mon Oct 29 15:49:09 2018 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.56.200', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Mon Oct 29 15:49:09 2018 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: my3306_binlog.000016, 965341200, 7390a401-b705-11e8-9ed9-080027b0b461:1-149275,
a4774e9e-bba9-11e8-bf3e-08002712513f:1-2
Mon Oct 29 15:49:09 2018 - [info] Executing master IP activate script:
Mon Oct 29 15:49:09 2018 - [info]   /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.56.100 --orig_master_ip=192.168.56.100 --orig_master_port=3306 --new_master_host=192.168.56.200 --new_master_ip=192.168.56.200 --new_master_port=3306 --new_master_user='mha_rep'   --new_master_password=xxx
Unknown option: new_master_user
Unknown option: new_master_password


IN SCRIPT TEST====/sbin/ifconfig eth0:0 down==/sbin/ifconfig eth0:0 192.168.56.111/24 up===

Enabling the VIP - 192.168.56.111/24 on the new master - 192.168.56.200 
bash: /usr/bin/arping: No such file or directory
Mon Oct 29 15:49:10 2018 - [info]  OK.
Mon Oct 29 15:49:10 2018 - [info] Setting read_only=0 on 192.168.56.200(192.168.56.200:3306)..
Mon Oct 29 15:49:10 2018 - [info]  ok.
Mon Oct 29 15:49:10 2018 - [info] ** Finished master recovery successfully.
Mon Oct 29 15:49:10 2018 - [info] * Phase 3: Master Recovery Phase completed.
Mon Oct 29 15:49:10 2018 - [info] 
Mon Oct 29 15:49:10 2018 - [info] * Phase 4: Slaves Recovery Phase..
Mon Oct 29 15:49:10 2018 - [info] 
Mon Oct 29 15:49:10 2018 - [info] 
Mon Oct 29 15:49:10 2018 - [info] * Phase 4.1: Starting Slaves in parallel..
Mon Oct 29 15:49:10 2018 - [info] 
Mon Oct 29 15:49:10 2018 - [info] -- Slave recovery on host 192.168.56.210(192.168.56.210:3306) started, pid: 16740. Check tmp log /var/log/masterha/app1/192.168.56.210_3306_20181029154904.log if it takes time..
Mon Oct 29 15:49:12 2018 - [info] 
Mon Oct 29 15:49:12 2018 - [info] Log messages from 192.168.56.210 ...
Mon Oct 29 15:49:12 2018 - [info] 
Mon Oct 29 15:49:10 2018 - [info]  Resetting slave 192.168.56.210(192.168.56.210:3306) and starting replication from the new master 192.168.56.200(192.168.56.200:3306)..
Mon Oct 29 15:49:10 2018 - [info]  Executed CHANGE MASTER.
Mon Oct 29 15:49:11 2018 - [info]  Slave started.
Mon Oct 29 15:49:11 2018 - [info]  gtid_wait(7390a401-b705-11e8-9ed9-080027b0b461:1-149275,
a4774e9e-bba9-11e8-bf3e-08002712513f:1-2) completed on 192.168.56.210(192.168.56.210:3306). Executed 0 events.
Mon Oct 29 15:49:12 2018 - [info] End of log messages from 192.168.56.210.
Mon Oct 29 15:49:12 2018 - [info] -- Slave on host 192.168.56.210(192.168.56.210:3306) started.
Mon Oct 29 15:49:12 2018 - [info] All new slave servers recovered successfully.
Mon Oct 29 15:49:12 2018 - [info] 
Mon Oct 29 15:49:12 2018 - [info] * Phase 5: New master cleanup phase..
Mon Oct 29 15:49:12 2018 - [info] 
Mon Oct 29 15:49:12 2018 - [info] Resetting slave info on the new master..
Mon Oct 29 15:49:13 2018 - [info]  192.168.56.200: Resetting slave info succeeded.
Mon Oct 29 15:49:13 2018 - [info] Master failover to 192.168.56.200(192.168.56.200:3306) completed successfully.
Mon Oct 29 15:49:13 2018 - [info] 

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

app1: MySQL Master failover 192.168.56.100(192.168.56.100:3306) to 192.168.56.200(192.168.56.200:3306) succeeded

Master 192.168.56.100(192.168.56.100:3306) is down!

Check MHA Manager logs at mysqldb2 for details.

Started manual(interactive) failover.
Invalidated master IP address on 192.168.56.100(192.168.56.100:3306)
Selected 192.168.56.200(192.168.56.200:3306) as a new master.
192.168.56.200(192.168.56.200:3306): OK: Applying all logs succeeded.
192.168.56.200(192.168.56.200:3306): OK: Activated master IP address.
192.168.56.210(192.168.56.210:3306): OK: Slave started, replicating from 192.168.56.200(192.168.56.200:3306)
192.168.56.200(192.168.56.200:3306): Resetting slave info succeeded.
Master failover to 192.168.56.200(192.168.56.200:3306) completed successfully.

6. 原mysqldb1手工加入集群

mysql> CHANGE MASTER TO MASTER_HOST='192.168.56.200', \
 MASTER_PORT=3306, \ 
 MASTER_AUTO_POSITION=1, \ 
 MASTER_USER='repl', \ 
 MASTER_PASSWORD='wanbin';

mysql> start slave;

7. 手工在线切换

masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.56.100 --orig_master_is_new_slave

转载于:https://www.cnblogs.com/wanbin/p/9899596.html

dbtrd733355
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
mysql宕机压测_利用sysbench工具测试MHA
weixin_28741413的博客
02-02 136
# masterha_master_switch --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.56.100 --master_state=dead --new_master_host=192.168.56.200 --ignore_last_failover--ignore_last_failover：在缺省情况下，如果MHA检...
达梦sysbench OLTP测试及数据库运维Linux常用指令汇总
最新发布
2401_84217518的博客
04-20 795
在linux系统中，我们创建一个新的文件或者目录的时候，这些新的文件或目录都会有默认的访问权限，umask命令与文件和目录的默认访问权限有关。rpm：管理rpm包的命令。另外，“~”也表示为home目录的意思，“.”是表示目前所在的目录，“..”则表示目前目录位置的上一层目录。more：一页一页的形式显示文件内容，更方便使用者逐页阅读，而最基本的指令就是按空白键（space）就往下一页显示，按 b 键就会往回（back）一页显示，而且还有搜寻字串的功能（与 vi 相似），使用中的说明文件，按 h。
MySQL 5.7和8.0 MHA架构下sysbench压测
cuihengju8933的博客
08-28 1007
sysbench压测环境： sysbench server：172.16.7.105 压测数据库服务器：MHA架构，172.16.7.100（主节点）、172.16.7.101、172.16.7.10...
Linux系统运维必备150个命令汇总
荒野求生的博客
03-24 1901
线上查询及帮助命令(2个) man：全拼manual，用来查看系统中自带的各种参考手册。 help：用于显示shell内部命令的帮助信息。 文件和目录操作命令(18个) ls：全拼list，列出目录的内容及其内容属性信息。 cd：全拼change directory，切换当前工作目录至dirName（目录参数）。其中dirName表示法可为绝对路径或相对路径。若目录名称省略，则变换至使用者...
阴沟翻船之 MYSQL MHA 故障 SSH timeout 与 Binlog not found
sql server的专栏
10-24 363
MYSQL MHA 的安装估计很多地方都是自动化安装的了，流水线方式。个人安装的MHA 的集群虽然没有几百台，但基本上已经突破了三位数，按理说安装应该是不会出什么奇怪的事情，但实际上每天...
性能测试工具sysbench简介
03-23
性能测试工具sysbench简介性能测试工具sysbench简介出处信息sysbench是一款开源的多线程性能测试工具，可以执行CPU/内存/线程/IO/数据库等方面的性能测试。数据库目前支持MySQL/Or 　您现在的位置：首页-->Oracle...
06-MySQL压力测试工具sysbench1
08-03
MySQL 压力测试工具 sysbench 介绍 sysbench 是一个模块化的、跨平台、多线程基准测试工具，主要用于评估测试各种不同系统参数下的数据库负载情况。目前 sysbench 主要支持 MySQL, pgsql, oracle 这 3 种数据库。 ...
Mysql基准测试工具-sysbench
03-23
Sysbench主要的测试方法有： 　之前介绍了相关mysql的性能参数调优，这些天利用基准测试工具对mysql的测试，Jason留下点Memory。 　Mysql数据库本身提供了比较优秀的性能测试工具，这里另外介绍下sysbench。 　...
Sysbench多线程性能测试工具
09-10
`Sysbench`是一款强大的多线程性能测试工具，主要用于评估系统的CPU、内存、I/O以及数据库性能。在本文中，我们将深入探讨`Sysbench`在MySQL数据库中的OLTP（Online Transaction Processing）测试，以及如何使用它来...
利用sysbench执行测试
老叶茶馆
04-17 972
*GreatSQL社区原创内容未经授权不得随意使用，转载请联系小编并注明来源。介绍新业务上线的时候通常需要对数据库性能进行压力测试，以确认是否满足需要，今天简单介绍下sysbench的用法：1.sysbench 是一个开源跨平台的多线程性能测试工具。2.可以用来进行 CPU、内存、磁盘IO、线程、数据库的性能测试。3.目前支持的数据库是 MySQL、Oracle 和 P...
mysql 报错10614_Sysbench 测试Mycat 连接丢失问题
weixin_35794185的博客
01-19 880
我也遇到相同的问题，mycat1.6, sysbench1.1sysbench /usr/local/share/sysbench/oltp_read_only.lua --mysql-user=test --mysql-password=test --mysql-port=8066 --mysql-host=127.0.0.1 --mysql-db=testdb --threads=1 run...
MySQL:MHA测试
Super菜的专栏
08-08 3029
测试配置： [server1] hostname=db42 candidate_master=1 check_repl_delay=0 port=3307 [server2] hostname=dbo_100_241  candidate_master=1 check_repl_delay=0 port=3307 [server3] hostname=db121
MYSQL使用MHA实现主从复制高可用、Galera Cluster介绍、压力测试、my.cnf配置参考
zerocdn的博客
03-01 548
MHA介绍 MHA： Master High Availability，对主节点进行监控，可实现自动故障转移至其它从节点；通过提升某一从节点为新的主节点，基于主从复制实现，还需要客户端配合实现，目前MHA主要支持一主多从的架构，要搭建MHA,要求一个复制集群中必须最少有三台数据库服务器，一主二从，即一台充当master，一台充当备用master，另外一台充当从库。 官网:https://code....
美团点评数据库高可用架构的演进与设想
美团技术团队
06-29 2888
本文介绍最近几年美团点评MySQL数据库高可用架构的演进过程，以及我们在开源技术基础上做的一些创新。同时，也和业界其它方案进行综合对比，了解业界在高可用方面的进展，和未来我们的一些规划和展望。 MMM 在2015年之前，美团点评（点评侧）长期使用MMM（Master-Master replication manager for MySQL）做数据库高可用，积累了比较多的经验，也踩了...
使用sysbench对mysql进行基准测试
evasnowind的专栏
11-27 728
文章目录测试环境说明硬件软件测试过程1. 测试innodb 100w条记录的读写性能1.1 生成100w数据1.2 进行读写测试1.2.1 第一次直接执行100w次读写1.2.2 第二次执行100w次读写1.2.3 第三次执行100w次读写1.3 清理数据2. 测试myisam 100w条记录的读写性能2.1 生成100w数据2.2 进行读写测试2.2.1 第一次执行100w次读写2.2.2 第二次执行100w次读写2.2.3 第三次执行100w次读写2.3 清理数据测试总结分析纵向对比横向对比其他图形化遇
Mysql8.0--性能测试对比（sysbench for MGR单主/MGR多主/MHA/Mysql单机）
zhangwenjiang001的博客
08-21 4934
环境说明： VMware虚拟机，CentOS Linux release 7.3，所有数据库的buffer_pool都设置为750M，仅限于OLTP事务测试，所有虚拟机节点在同一台物理机上； MGR单主：mysql 8.0.11，三个节点； MGR多主：mysql 8.0.11，三个节点； MHA（开半同步复制）:mysql 5.7.19，三个节点； Mysql单机：mysql 5.7....
MySQL数据库（九） 集群 Cluster 和性能优化
崔庆贺的博客
07-05 3310
文章目录6 MySQL 集群 Cluster6.1 MySQL主从复制6.1.1 主从复制架构和原理6.1.2 实现主从复制配置6.1.3 主从复制相关6.1.4 实现级联复制6.1.5 主主复制6.1.6 半同步复制6.1.7 复制过滤器6.1.8 主从复制加密6.1.9 GTID复制6.1.10 复制的监控和维护6.1.11 复制的问题和解决方案6.2 MySQL 中间件代理服务器6.2.1 关系型数据库和 NoSQL 数据库6.2.2 数据切分6.2.3 MySQL中间件各种应用6.2.4 Mycat
MySQL server has gone away 问题的解决方法
lizhongren的专栏
11-08 1455
应用程序（比如PHP）长时间的执行批量的MYSQL语句。执行一个SQL，但SQL语句过大或者语句中含有BLOB或者longblob字段。比如，图片数据的处理。都容易引起MySQL server has gone away。 今天遇到类似的情景，MySQL只是冷冷的说：MySQL server has gone away。 大概浏览了一下，主要可能是因为以下几种原因： 一种

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值